Audit a project's npm dependencies

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

No annotations are provided, so the description carries full burden. It discloses that the tool queries the npm registry and produces a report with specific fields. However, it doesn't state whether the tool is read-only, potential rate limits, or failure modes. The 'real registry facts' line adds rationale rather than behavioral detail.

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 exactly two sentences with no filler. The first sentence front-loads the core purpose and outputs. The second sentence provides clear usage guidance and input preparation. Every word earns its place.

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?

Without an output schema, the description adequately lists the return fields (patch/minor/major, versions behind, deprecated, license) and gives strong usage context. It could mention edge cases (e.g., invalid package.json, registry unavailability) or error handling, but for an audit tool the key information is present.

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 each parameter described. The description adds value by directing the agent to read the repo's package.json and pass it as the `packageJson` parameter, which clarifies the expected input. It doesn't expand on includeDev/includePeer beyond the schema definitions.

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 reports each dependency's freshness against the npm registry, including how far behind (patch/minor/major), versions behind, deprecated status, and license. This is a specific verb+resource with concrete outputs. However, it does not differentiate itself from the sibling tool 'check_package'.

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 gives trigger phrases ('update dependencies', 'check what's outdated', 'is anything deprecated') and context (before a dependency bump). It also instructs the agent to read the repo's package.json and pass its full text. It lacks exclusions or mentions of alternatives, so not a 5.

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