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

Annotations already declare readOnlyHint=true, so the tool is known to be a safe read operation. The description adds that inputs are 'validated server-side' and that the deliverable is 'audited,' which are useful. However, it also includes irrelevant promotional content and doesn't disclose pagination, rate limits, or any other behavioral constraints.

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 description is three sentences, but the third sentence is a reference-case marketing paragraph that doesn't help with tool usage. The first two sentences are useful, but the overall structure mixes purpose with unrelated promotion, making it less concise than it should be.

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?

Given the tool's complexity (nested objects, 7 parameters) and lack of an output schema, the description is insufficient. It doesn't explain the structure of the returned deliverable, the meaning of key fields like outcome, dealValueEur, or how the analysis works. The vague 'documented case fields' fails to compensate for the 14% schema coverage.

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 only 14% (only async has a description). The description does not explain any of the parameters or nested fields. 'Send the documented case fields' is vague and doesn't help an agent understand what data to provide for company, product, deals, or optional fields.

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 states a specific verb and resource: 'Analyse Win/Loss deals'. It adds 'Returns a structured, audited deliverable,' which clarifies the output. However, it doesn't explicitly distinguish from sibling tools like deal_coach or battle_cards_live, though the Win/Loss focus is relatively unique.

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 no guidance on when to use this tool versus alternatives. The reference case and 'Gapup agent-payable C-suite expertise' are promotional rather than practical usage context. No mention of alternative tools or exclusion criteria.

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