npm_scripts

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

Describes script extraction and flagging of suspicious commands, but does not disclose whether scripts are executed, read-only nature, or any other behavioral traits. With no annotations, more detail expected.

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 front-loaded with purpose. No redundant words, efficient communication of functionality.

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?

Simple tool with 2 parameters and no output schema; description adequately covers functionality. Could mention return format or error handling, but not critical for a focused analysis tool.

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 already describes both parameters (name and version) with clear descriptions; description adds no extra meaning. Baseline 3 justified as schema coverage is 100%.

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 the tool extracts and analyzes lifecycle scripts from a specific npm package version, with specific mention of flagging suspicious commands. Distinguishes itself from sibling tools focused on general package info or other aspects.

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?

Implied usage for analyzing lifecycle scripts in supply chain attacks, but no explicit guidance on when to use vs alternatives (e.g., npm_package). Missing when-not conditions.

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