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

Goes well beyond the annotations: it discloses that a human replies asynchronously by email to the supplied address, that the return value is a T-XXXXXX ticket ref, and warns against including secrets, API keys, or wallet keys. The annotations only declare it is non-read-only and non-destructive; the description adds the async human-handling model and the security caution, though it does not state SLA, auth prerequisites, or whether duplicate tickets are created on retry (idempotentHint=false is left unexplained).

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?

Four short sentences, front-loaded with the action and scope, then precondition, then return behavior, then safety warning — a sensible priority order. Minor redundancy between the parenthetical topic list and the topic enum in the schema.

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 four-parameter, no-output-schema tool this is essentially complete: the agent knows the purpose, what to supply, what comes back (a ticket ref), how the reply arrives, and what not to put in the message. Nothing needed to invoke it correctly is missing.

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 coverage is 75%, so the baseline is 3. The description reinforces the optional order parameter ('order_id or its SD- ref') and clarifies that email is where the reply lands, but those points largely duplicate the schema descriptions; the only genuinely new constraint is the caution about message content, which is security advice rather than semantic clarification of a field.

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?

Specific verb plus resource: 'Open a support ticket with a person at StableDomains', scoped to a named set of issue types. An agent can tell instantly this is the human-escalation tool, distinct from self-service siblings like check_order or get_dns.

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?

Lists the qualifying issue categories (order, payment, DNS, transfer, account, abuse) and instructs the agent to pass the order id or SD- ref when one exists, which is actionable routing guidance. It does not explicitly say when to prefer self-service siblings first, so it stops short of full when/when-not coverage.

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