Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It explains that it fetches package.json/requirements.txt, runs behavior commitment scoring, and returns a risk table with specific flag criteria (CRITICAL, HIGH, WARN). It does not mention network/rate limits or authentication, but given it's a read-only audit, the disclosure is solid and adds context beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and uses well-separated sections (risk flags, examples, usage trigger). Every sentence adds value; the length is justified by the lack of annotations and output schema. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema and no annotations, the description covers the process, inputs, and the meaning of risk levels, giving a comprehensive picture. It stops short of describing the exact response structure (e.g., JSON shape) but provides enough for an agent to know what to expect. A perfect score would require more detail on output format or edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema's description for 'repo' already covers accepted formats ('owner/repo', GitHub URL) and provides examples. The tool description repeats some examples but adds no new parameter-level meaning. Since schema coverage is 100%, the baseline of 3 is appropriate—the description does not need to compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Audit the supply chain risk of a GitHub repository's dependencies.' It specifies the verb (audit), resource (GitHub repository's dependencies), and method (fetches package.json/requirements.txt, runs behavioral commitment scoring). It also provides examples and distinguishes from siblings by being GitHub-specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Use this when someone asks "is my project at risk?" or "audit this repo's dependencies"' and highlights it as 'the fastest way to audit a project.' It does not explicitly name alternatives or when not to use it, but the GitHub-specific focus and examples provide clear context. Since it lacks explicit exclusions or alternative references, it slightly misses a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.