Check Dependencies

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

Annotations indicate readOnly, idempotent, non-destructive. Description adds details on return structure {findings, total, by_severity, summary} and explains when fixed_in is omitted, providing behavioral context beyond annotations.

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?

Description is somewhat long but well-structured: first sentence summarizes purpose, then provides usage, rate limits, return format, and special cases. Every sentence adds value, though slight trimming possible.

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 complexity of multiple package managers, bulk query limit, and return format, description covers all essential aspects including edge cases (open-ended version ranges). Output schema exists but description complements it.

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 coverage is 100% with detailed description of packages parameter. Description adds context on supported package managers (npm/PyPI etc.) and CVE database source, augmenting schema meaning.

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?

Description clearly states 'Audit project dependencies against CVE database: find known vulnerabilities in your package list.' It uses specific verbs and resources, and distinguishes from siblings like cve_lookup by specifying bulk query of packages.

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?

Explicitly states 'Use for dependency security scanning; use cve_lookup for single CVE.' Also provides rate limits for Free and Pro tiers, guiding appropriate usage.

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