supply_chain_audit

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

Annotation sets destructiveHint=true but description says 'reads local filesystem', which is contradictory and not explained. No disclosure of whether scripts are executed or files modified.

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?

Compact description with front-loaded purpose; every sentence adds unique detail. Minor improvement could combine lines.

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?

Adequate for a simple one-param tool with annotations, but no output schema and lack of clarification on destructive hint leaves gaps for agent decision-making.

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?

Single parameter 'path' with schema description specifying absolute path and required files. Description adds minimal extra value beyond schema (checks node_modules). Baseline 3 due to 100% schema coverage.

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?

Clearly states the tool audits Node.js dependencies for supply chain attack indicators, listing specific checks (dangerous lifecycle scripts, typosquatting, eval). Distinguishes from siblings like port_scan or check_cves.

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?

Provides context about reading local filesystem and not using remote services, implying privacy benefit. However, no explicit when-not-to-use or comparison to alternatives among siblings.

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