Audit npm dependencies

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

Discloses cap of 50 packages and output structure (verdict + summary). No annotations provided, so description carries burden; lacks details on whether it mutates anything or if it's read-only.

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?

Two concise sentences covering purpose, inputs, use case, and limit. No wasted words.

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?

With output schema present, description covers all necessary context: purpose, inputs, usage, and constraints. No gaps.

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%, so baseline 3. Description adds concrete examples for packages and explains that package_json extracts all dependency sections, adding value beyond 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?

Clearly describes auditing many npm dependencies and returning per-package verdicts plus summary. Distinct from sibling check_package_fitness by focusing on bulk audit.

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 it's ideal for CI/pre-merge dependency gates and mentions 50-package cap. Could explicitly contrast with sibling but context makes it clear.

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