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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavior beyond that: price book ordering ('most used first'), the 12-month window on stats, and the conditional VAT warning that only appears for non-VAT-registered businesses. It does not say what happens with an invalid or expired key, which is the main residual gap.

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?

One dense sentence that front-loads the primary payload (settings, price book) and closes with the conditional edge case. Nothing is padded or repeated, though the parenthetical stats definition makes the sentence long enough that a slight structural break would aid scanning.

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?

There is no output schema, so the description must carry the return-value burden, and it enumerates every category of data returned, including the conditional VAT warning. With one fully documented parameter and complete annotations, an agent has what it needs to select and call this tool correctly.

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 and 100% schema description coverage, the schema already explains that trade_key is the secret key from setup_trade beginning 'qbk_'. The description adds no further meaning about the key or its failure modes, 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 description names the concrete payload: saved settings, price book, quote stats (win rate, value won over 12 months), and a VAT-threshold warning. That is far more specific than a restatement of the name 'get_trade'. It stops short of explicitly contrasting with get_quote or list_quotes, so an agent must infer that this is the business-level aggregate rather than per-quote data.

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?

Usage is only implied: the listed contents suggest 'call this to view the business profile and performance stats'. There is no stated when-to-use, when-not-to-use, or named alternative such as get_quote for a single quote. The only routing hint comes indirectly from the required trade_key referencing setup_trade.

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