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

Annotations already indicate readOnly, idempotent, openWorld, non-destructive. The description adds critical behavioral details: returns specific fields (IDs, titles, prices, bid counts, time left), supports pagination and sort. No contradictions.

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: front-loaded with purpose and return values, followed by authentication and features. Every sentence adds value with no 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?

No output schema, but the description explicitly lists what is returned (item IDs, titles, prices, etc.) and mentions pagination and sort. This is complete for a search tool with moderate complexity.

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 the baseline is 3. The description adds value with examples, clarifies that _apiKey is the authentication method, and notes pagination/sort capabilities, which aids parameter understanding 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 searches active GunBroker listings by keyword, and lists returned fields (item IDs, titles, prices, etc.). It distinguishes from sibling tools like gunbroker_get_item (detail retrieval) and gunbroker_seller_orders (orders).

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 context: public tool needing only a developer key. It implies usage for keyword searches but does not explicitly state when not to use or name alternatives. However, it is clear enough for an agent to select it for basic searches.

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