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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful context by specifying that it audits 'exact' dependencies and returns affected packages and vulnerabilities, which goes beyond the annotation safety profile.

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 a single sentence that is front-loaded with the action and resource, with no redundant words. The enumeration of ecosystems is necessary for clarity and does not feel excessive.

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?

Given the presence of annotations and an output schema, the description is complete enough: it clearly states the purpose, target ecosystems, and the return type. It does not mention input limits or exact version formatting, but those are covered by the input schema.

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?

Schema description coverage is 0%, but the description enumerates the supported ecosystems (matching the schema enum), providing some semantic value. However, it does not explain the dependencies array structure (name/version) or constraints like max 100 items, leaving that to the schema.

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 uses a specific verb ('Audit') with a clear resource ('dependencies') and scope ('against OSV'), and states the result ('return affected packages and vulnerabilities'). It clearly distinguishes from sibling tools like license-audit by focusing on vulnerability auditing across multiple ecosystems.

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 implies when to use (auditing dependencies for known vulnerabilities) but does not explicitly state when not to use or reference alternatives. It lacks exclusions or a comparison with sibling audit tools, leaving the agent to infer usage from context.

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