get_package_info

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

With no annotations, the description does most of the work. It discloses the return behavior ('Returns versions list, homepage, repository, and full package details') but doesn't cover other behavioral aspects like rate limits, authorization, or whether results are cached. For a read-only 'get' tool, this is adequate but not exceptional.

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 sentences, no filler. The first sentence states purpose, the second adds use cases and return details. Fully front-loaded and 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?

For a read-only package info tool, the description covers what, when, and what comes back. The lack of an output schema is acceptable given the description explicitly lists the key fields. It doesn't explain how to handle errors or edge cases, but those aren't essential for this simple 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 description coverage is 100%, so parameters are already well-documented. The description adds no additional semantics beyond what's in the schema, making the baseline 3 appropriate.

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 'Get detailed package information including all versions' with a specific verb and resource. It explicitly differentiates from siblings like get_latest_version and check_version_exists by emphasizing comprehensive metadata and all versions.

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 provides explicit use cases: 'Use for dependency audits, security reviews, or when you need comprehensive package metadata.' It does not mention when not to use or alternatives, but the context is clear enough to distinguish this from simpler sibling tools.

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