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

With no annotations provided, the description carries the full burden, and it does well: it discloses the 'add to open one with same symptom' behavior, the automatic call attachment, and the return payload (ticket reference, status, suggested path). It leaves out potential side effects or authorization requirements, but the disclosed behavior is substantive.

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 two sentences with no filler. It front-loads the core action, then adds behavior and return-value details in a compact way. Every phrase contributes to choosing and invoking the tool correctly.

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 no annotations and no output schema, the description is unusually complete: it covers the triggering condition, the deduplication behavior, the key parameter integration, and the return shape. Nothing critical is missing for an agent to call this tool correctly.

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 100%, so the baseline is 3, but the description adds meaningful cross-parameter guidance: quoting the request_id connects the error body to the exact call and the suggested fix. It also clarifies that request_ids inside the message body are picked up automatically, which the schema alone does not state.

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 opens with a specific verb—'Open a support ticket for this account'—and clearly distinguishes this from sibling tools like get_ticket, list_tickets, and reply_ticket. The added detail about attaching the request_id and the behavior of adding to an existing open ticket makes 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 gives clear context for when to use the tool: after a failed call, quote the request_id from the error body. It also explains the deduplication behavior with the same symptom. It does not explicitly name alternative tools like explain_error, but the condition for use is clear enough that an agent can decide correctly.

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