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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds nothing beyond that — no note on what is returned, error behavior on a missing/invalid id, or scope of the 'query' object. It also repeats the same path sentence twice, adding no information.

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 single substantive sentence is duplicated verbatim, and the operation-ID / describe_operation metadata is filler relative to the tool's purpose. It is short but wasteful rather than front-loaded with useful information.

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, 0% parameter documentation, and a nested free-form 'query' parameter, the description should carry more weight. It only redirects to describe_operation, leaving an agent unable to know what fields to pass or what a ticket response contains.

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% for 2 parameters, and the description does not compensate. The ':id' path token weakly implies that params.id is the ticket identifier, but nothing explains the free-form 'query' object or id format/length constraints.

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 REST path 'GET /api/support/tickets/:id' does convey a verb and a resource (fetch one ticket by its id), so an agent can infer the purpose. But it is literally the title and tool name restated, and gives no differentiation from nearby siblings such as get_support_tickets (list) or get_support_tickets_by_id_messages.

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?

There is no statement of when to use this tool versus the sibling list/messages/stats ticket endpoints. The only actionable sentence points to describe_operation for request schemas, which is schema discovery help, not usage guidance.

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