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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the domain note about instant quotes but says nothing about pagination semantics despite limit/cursor existing. With annotations carrying the safety bar, this is adequate but thin.

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 short sentences, front-loaded with the core purpose and zero padding. The trailing quote sentence is arguably tangential to invoking the tool, keeping it just below maximum.

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?

An output schema exists, so return values needn't be described, and annotations cover the safety profile. However, the tool exposes a cursor/limit pagination surface and a query filter that are entirely undocumented anywhere, leaving the agent to guess their meaning.

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 0% across all three parameters (limit, query, cursor), so the description carries the full burden of explaining them. It adds nothing: no mention of what query filters on, how cursor pagination works, or that limit is capped at 20.

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?

States a specific verb and resource: 'List Tradehand's canonical UK trades.' An agent understands this returns a catalogue of trade categories. It does not, however, differentiate itself from the sibling search_traders or explain what 'canonical' excludes.

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 second sentence ('Instant quote is available before a trader is assigned') is a domain fact, not guidance on when to call this tool versus get_service_options or search_traders. No conditions, prerequisites, or exclusions are given for using browse_trades.

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