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

The description directly contradicts the annotations. The annotations declare openWorldHint=true, but the description says 'no external research or outbound actions.' Additionally, destructiveHint=true is inconsistent with a summarization tool that 'Returns a draft for human review' and does not modify anything. The description does disclose price and payment requirements, but these contradictions are severe and misleading.

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, using only three sentences. It front-loads the core purpose, then clarifies scope and constraints, and ends with pricing and authorization details. There is minimal verbosity, and the structure flows logically. The inclusion of price and payment information is efficient and relevant.

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 has five parameters, no output schema, and annotations that are contradictory, the description is incomplete. It lacks details about the input structure, expected output format, and payment process (only mentions 'explicit wallet authorization' without specifics). The contradictions further reduce completeness, as an agent cannot reliably determine the tool's actual behavior. The description would need to clarify the parameter semantics and resolve the annotation conflicts to be considered complete.

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%, so the description must compensate for the undocumented parameters. It mentions 'supplied account outcomes, unresolved issues, renewal objectives, and questions' which loosely correspond to the input fields, but it does not name or explain any of the five parameters (input, result_expires, idempotency_key, result_signature, payment_signature). The description provides no guidance on how to populate the required 'brief' and 'source_text' fields or the optional 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's function: 'Summarize supplied account outcomes, unresolved issues, renewal objectives, and questions.' It specifies a distinct resource (renewal brief) and explicitly excludes CRM access, which differentiates it from other summary tools in the sibling list. The verb 'Summarize' and the detailed scope make the purpose unambiguous.

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 implies usage when all needed information is supplied by the buyer, stating 'Uses buyer-supplied information only; no external research or outbound actions.' However, it does not provide explicit when-to-use guidance, alternatives, or conditions that would route an agent to this tool over similar summary tools like tradepilot_service_document_summary or tradepilot_service_executive_brief. No exclusions or comparisons are given.

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