descriptions

descriptions is a skill for Claude Code, Codex from gobeyondidentity/bi-mcp. It costs 0 tokens per session (400 once invoked), scanned A, original, Apache-2.0.

A writing guide for documenting tools used by AI agents. It explains what each tool does, what it needs first, what it returns, and any important limitations.

In plain words
What is it for?
Writing short tool descriptions in JSON files, including links between tools that must be used in a particular order.
Why use it?
It helps agents choose the right tool and call it correctly. Clear prerequisites and results reduce failed or incomplete tool calls.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Writing short tool descriptions in JSON files, including links between tools that must be used in a particular order.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gobeyondidentity/bi-mcp/descriptions
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add gobeyondidentity/bi-mcp --skill descriptions
Clone the repo
git clone --depth 1 https://github.com/gobeyondidentity/bi-mcp

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for descriptions

README.md
[![agentmods](https://agentmods.dev/badge/skills/gobeyondidentity/bi-mcp/descriptions/github.svg)](https://agentmods.dev/skills/gobeyondidentity/bi-mcp/descriptions)
Your own site
<a href="https://agentmods.dev/skills/gobeyondidentity/bi-mcp/descriptions"><img src="https://agentmods.dev/badge/skills/gobeyondidentity/bi-mcp/descriptions/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for descriptions

Your own site · 80×15
<a href="https://agentmods.dev/skills/gobeyondidentity/bi-mcp/descriptions"><img src="https://agentmods.dev/badge/skills/gobeyondidentity/bi-mcp/descriptions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 400 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00400
Opus 5 $0.00000 $0.00200
Sonnet 5 $0.00000 $0.00080
Haiku 4.5 $0.00000 $0.00040

Measured 10d ago against content hash 86c4f810254f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

descriptions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

descriptions/SKILL.md · 39 lines

What it actually says

Writing Tool Descriptions

Goal

Write descriptions that help AI agents understand what each tool does, what prerequisites it has, and how it relates to other tools. A good description answers:

  • What does this tool do?
  • What do I need before I can call it? (e.g. "requires a group_id — use list_groups first")
  • What does the response contain?
  • Any gotchas or important context?

Where to find the services

The Beyond Identity platform services live at $ZEROPW/. Inspect the relevant service code to understand what each endpoint actually does, what validations it performs, and what side effects it has. This will help you write descriptions that go beyond the OpenAPI summary.

Format

  • Write descriptions as plain strings in v1.json or v0.json, keyed by tool name
  • Keep descriptions under 500 characters — concise but complete
  • Mention prerequisite tools by name (e.g. "use list_groups to get a group_id")
  • Mention what the response includes when it's not obvious

Example

{
  "add_group_members": "Add one or more identities as members of an existing group. Requires a group_id (use list_groups or create_group first) and an array of identity_ids (use list_identities to find them). Members added to a group inherit any roles assigned to that group."
}

Workflow

  1. Pick a tool from v1.json or v0.json that has no entry yet, is weak, or is specified by the user
  2. Find the corresponding service handler in $ZEROPW/ by searching for the operation name or URL path
  3. Read the handler to understand validations, side effects, and relationships
  4. Write a description and add it to the JSON file
  5. Run npm run generate to apply the override
  6. Run npm run build to verify everything compiles
Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 39 lines · 0 tokens per session scan A 86c4f810254f

Subscribe to this mod's changes

descriptions is a skill published in the GitHub repository gobeyondidentity/bi-mcp (0 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 400 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens