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

Annotations already declare non-readOnly, openWorld, non-idempotent, non-destructive. The description adds genuinely new context beyond that: the follow-up/continuation model (ticketId + replyToken) that explains the idempotentHint=false repeated-call behavior, and a safety constraint ('Never seed phrases or keys') that annotations don't cover. No rate limits or response shape, but the security note is valuable added behavior.

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?

Three short front-loaded fragments with no filler; the primary use case leads and the security caveat is last. The telegraphic style is efficient but slightly clipped, costing a bit of parseability rather than words.

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?

An output schema exists, so return values needn't be described, and 88% schema coverage handles most parameters. The description covers the essential triggering scenarios, the follow-up flow, and a security constraint, which is adequate for an 8-param, 1-required tool. Minor gaps remain around when this beats request_agent_key or submit_feedback.

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 88%, so the schema already documents nearly all 8 parameters (message, orderId, category, sessionId, walletAddress, patterns). The description reinforces the ticketId+replyToken pairing for follow-ups but adds little syntax or meaning beyond what the schema states ('With ticketId.'). Baseline 3 is appropriate given the schema does the heavy lifting.

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 name/title give the specific verb+resource (open a support ticket), and the description pins the triggering scenarios ('Stuck or failed swap, or a question') and names the sibling get_support_ticket as where answers arrive. An agent can distinguish creating a ticket from reading one without opening a schema, though the telegraphic phrasing leaves the 'create' action implicit rather than stated.

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?

Explicit when-to-use triggers are given ('stuck or failed swap, or a question') plus the follow-up path ('Follow up with ticketId + replyToken'). It routes to get_support_ticket for retrieving answers. What's missing is an explicit when-not (e.g., when to prefer submit_feedback or request_agent_key instead).

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