Get npm Package Info

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

Annotations already confirm safe, idempotent, read-only behavior. The description adds value by detailing the comprehensive return structure (license, repository, keywords, etc.), providing transparency about the output 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?

The description is concise (about 10 lines) with clear sections for Args, Returns, and Examples. It is front-loaded with the purpose, and every sentence adds value without redundancy.

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 a single parameter and no output schema, the description fully explains the return fields (version, license, maintainers, etc.) and provides examples. No gaps remain for correct invocation.

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 has 100% coverage with a clear description for package_name. The tool description reinforces this with examples (e.g., 'react', '@anthropic-ai/sdk') and shows how to invoke, adding semantic clarity beyond the 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?

The description 'Get comprehensive information about an npm package' clearly states the action and resource. It lists specific data fields (latest version, description, license, etc.) and distinguishes from siblings like npm_package_dependencies and npm_package_readme.

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 implies usage by listing the information returned, but does not explicitly state when to use this tool versus alternatives like npm_package_dependencies or npm_search. No when-not or alternative guidance is provided.

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