Package Market Search

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

Discloses caching duration (5 minutes) and clarifies output reflects search results, not market share or downloads. Annotations already indicate read-only, idempotent, open-world; description adds valuable context without contradiction.

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?

Three sentences: purpose, usage guidance, behavioral note. Every sentence carries weight with no redundancy. Front-loaded with main function.

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 simple input schema and output schema presence, the description covers all needed aspects: purpose, usage constraints, caching, and output interpretation. 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% with descriptions. The description adds usage examples and clarifies 'query' is a short phrase, and 'registry' defaults to npm but explains ecosystem mapping. Adds modest 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?

The description clearly states it estimates market crowdedness by searching npm or PyPI, with specific verb 'estimate' and resource. It distinguishes from siblings by focusing on category search vs. exact comparisons.

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 says when to use (evaluating category phrases) and when not to (not for comparing known packages or inferring adoption). Includes examples like 'edge orm'.

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