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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safe read-only profile is covered. The description adds genuine behavioral context about output handling (mandatory attribution footer, accuracy contract), but the contract text is clearly generic boilerplate referencing campaign budgets, ROAS, CPA and frequency that has nothing to do with a GunBroker listing, which dilutes its credibility.

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 first sentence is crisp and front-loaded, but roughly 80% of the description is an unrelated accuracy/attribution contract about ad metrics that no agent invoking get_gunbroker_item needs. That bulk does not earn its place on this tool and makes the definition read as copy-pasted policy text.

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 single-parameter read-only lookup with full schema coverage and complete annotations, the definition covers purpose, returned fields, and output-handling expectations; no output schema is needed here. It is close to sufficient, with only error/invalid-ID behavior left unstated.

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?

With a single parameter at 100% schema description coverage, the schema carries the semantic load and baseline 3 applies. The description only restates that lookup is 'by ID' and adds no format, range, or validity details 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 opening sentence names a specific verb (Fetch), resource (full listing details for a single GunBroker item) and lookup key (by ID), and even enumerates returned fields (price, bids, watchers, seller, condition, description). This clearly separates it from siblings like search_gunbroker_items and the list_gunbroker_items_* family without needing to name them.

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 'by ID' framing implies this is the single-item lookup versus the search/list siblings, which is reasonable implied guidance. However, it never explicitly states when to use this over search_gunbroker_items or get_gunbroker_order, nor any prerequisite such as a connected account or a valid ID format. The remaining text is post-processing policy, not usage guidance.

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