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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: an attribution-footer obligation and a data-accuracy/derived-metric contract. However, the contract text references campaign budgets, ROAS, CPA and frequency, which are incoherent for a GunBroker order tool and dilute the value.

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 well front-loaded, but roughly three quarters of the description is a generic accuracy/attribution boilerplate block whose metric list (ROAS, CPA, campaign budgets, frequency) is irrelevant to this tool. Those sentences do not earn their place here.

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, single-parameter tool with no output schema, the description covers the resource, the scope, and the returned detail categories well enough to call it correctly. The only shortfall is the missing sibling routing and the off-topic boilerplate.

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% and there is a single parameter (order_id) fully documented in the schema. The description adds no syntax, format, or lookup guidance beyond it, so the baseline of 3 applies.

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 gives a specific verb and resource ('Fetch full details for a single GunBroker order') and enumerates the detail categories returned (buyer, item, payment, shipping, FFL transfer). The word 'single' implicitly separates it from list_gunbroker_orders, but no sibling is named explicitly.

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?

There is no when-to-use guidance, no prerequisites (e.g., needing an order ID from list_gunbroker_orders), and no routing advice versus list_gunbroker_orders or get_gunbroker_item. The remaining text is output-handling 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.