npmDeps

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint – description adds no behavioral context beyond stating 'dependencies and devDependencies'. Does not disclose caching details, rate limits, or error handling. With annotations, the description's contribution is minimal but not contradictory.

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?

Single sentence, front-loaded with action ('Analyze'), immediate resource identification. No fluff. Could slightly expand without harming conciseness, but current is efficient.

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?

Output schema exists, so return details not needed. However, given many sibling tools, more context on scope (e.g., whether it deep-resolves transitive deps, version handling) would improve agent selection. Currently adequate but uninformative.

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?

Input schema covers 100% of parameters with descriptions (packages, ignoreCache). Tool description adds no additional meaning to parameters – baseline 3 applies as schema does the heavy lifting.

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 explicitly states 'Analyze dependencies and devDependencies of an NPM package' – clear verb+resource. Differentiates from siblings like npmVersions (versions), npmLatest (latest version), npmVulnerabilities (security) by focusing specifically on dependency analysis.

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?

No guidance on when to use this tool vs alternatives (e.g., npmVulnerabilities for security, npmTypes for type definitions). No mention of prerequisites, input format (e.g., version suffixes), or conditions favoring this tool over other dependency-related tools.

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