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

Annotations already declare readOnlyHint=true, and the description only restates 'Read-only' rather than adding to it. It does disclose the breadth of retrieved content (conversation thread, attachment names, related cluster), which is useful context, but says nothing about permissions, redaction, or pagination/size limits.

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?

Front-loads the returned content, then identification keys and two short routing/behavioral sentences. No filler, no repetition of the schema, and the most important clause (what you get back) comes first.

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?

With no output schema, the description carries the burden of describing return content and does so thoroughly, and it is a read-only tool whose only annotation is already restated. Nothing an agent needs to select and invoke it 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 100%, so the baseline is 3, but the description adds real meaning: ticket_number is 'the number people quote', and either identifier may be used. That interprets the practical difference between the UUID and the per-organisation number beyond the schema's mechanical wording.

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?

States a specific verb ('Show one support ticket in full') and enumerates exactly what comes back: subject, description, status, severity, related cluster, reporter, conversation, attachment names. It also names the two accepted identifiers, so an agent knows precisely what this returns versus list_support_tickets or close_support_ticket.

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?

It explicitly routes the agent to a sibling: 'To answer a question support asked, use comment_support_ticket.' That is a clear when-to-use-this-instead condition. It does not, however, disambiguate against the near-duplicate ticket_get/ticket_list family, and gives no negative guidance (e.g. use list_support_tickets for browsing many tickets).

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