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

The description directly contradicts the provided annotations: annotations declare openWorldHint=true while the description claims 'Uses buyer-supplied information only; no external research or outbound actions.' This is an annotation contradiction that undermines trust in the tool's stated side effects and scope.

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 compact and front-loaded: the core purpose comes first, followed by constraints, return format, and pricing. Every sentence adds useful information with no filler.

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?

For a tool with nested required input and no output schema, the description is incomplete: it does not explain how to populate the required nested fields or any of the optional signature/idempotency parameters, nor what the returned draft structure looks like. The contradiction about external actions further reduces the completeness of the behavioral picture.

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 5 undocumented parameters. It vaguely maps to the input by mentioning 'support-ticket text,' but it never explains 'brief', 'audience', 'result_expires', 'idempotency_key', 'result_signature', or 'payment_signature'.

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 uses a specific verb chain — classify, summarize, propose diagnostics, draft a response — and names the resource (support-ticket text) precisely. It also distinguishes itself by explicitly saying the response is a draft and is not sent. This is a clear and unambiguous purpose statement.

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 gives usable context for when to use it: when you have supplied support-ticket text and want a triage draft for human review. It also includes when-not-to-use signals such as 'without sending it' and 'no external research or outbound actions'.

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