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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond that — no note on pagination, result volume, permissions, or whether messages include attachments/threading.

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 sentence is duplicated verbatim, wasting half the description, and the operation ID adds no agent-relevant information. There is no front-loaded statement of purpose beyond the raw path.

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, no annotations gap-filling needed, and 0% parameter coverage, the description should carry the burden of explaining inputs and return shape. Instead it provides neither, leaving a nested-object 'query' parameter completely undocumented.

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 two parameters (a free-form 'query' object and required 'params.id'). The path template ':id' implies the id is the ticket identifier, but the description never explains the 'query' parameter, its accepted keys, or id format 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 description is essentially the raw HTTP path repeated twice ('GET /api/support/tickets/:id/messages'), which restates the tool name/title rather than describing the operation in agent-facing terms. An agent can infer it retrieves messages for a support ticket, but nothing states ordering, pagination, or what a 'message' contains.

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?

No when-to-use or when-not-to-use guidance is given. The only actionable pointer is 'describe_operation provides native request schemas', which redirects the agent to another tool rather than explaining selection criteria versus siblings like get_support_tickets_by_id or get_support_tickets.

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