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

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds server-side validation and an audited deliverable, which are useful behavioral details beyond the annotations. No contradictions detected.

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 concise, with the purpose front-loaded. The reference case adds length but provides a concrete example without being verbose. Overall, each sentence contributes meaning.

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 a complex nested schema with 6 parameters and no output schema, the description is too sparse. It doesn't describe expected deal fields, scoring logic, or result format beyond 'structured deliverable.' The reference case hints at metrics but is insufficient for a tool of this complexity.

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 17% (async only). The description does not explain company, product, deals, salesCycle, or targetWinRate. It only vaguely says 'send the documented case fields,' providing almost no semantic value for the parameters.

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 clearly states the tool scores the pipeline against the MEDDIC framework and returns a structured, audited deliverable. This is a specific verb+resource combination that distinguishes it from generic sales tools, though it doesn't explicitly name sibling alternatives.

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 context 'Gapup agent-payable C-suite expertise (CRO)' implies the tool is for MEDDIC scoring in sales pipelines, but there is no explicit when-to-use or alternatives guidance. The usage is implied rather than clearly delineated.

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