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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description usefully adds that returned content includes the full conversation with Tango staff replies, but omits pagination, result limits, and any auth constraints.

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?

Two front-loaded sentences plus an API reference link; every sentence carries information and the key conditional (ticket_id) is stated early. The trailing URL is marginally verbose but genuinely useful.

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 2-param read tool with a rich enum and readOnly annotations, the essentials are present. Gaps remain: no mention of status filtering behavior, result volume/pagination, or ordering, and there is no output schema to compensate.

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 50%: ticket_id is documented in the schema and the description reinforces its effect (fetch one thread instead of the list). The status enum is undocumented in both places, though its values are largely self-explanatory, so baseline 3 is appropriate.

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 gives a specific verb+resource (list support tickets) and clarifies the dual mode: reading full conversations and fetching a single thread via ticket_id. It implicitly distinguishes itself from the action siblings (submit_support_request, reply_to_support_request), though it never names them.

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 gives concrete conditional guidance for one mode ('Pass ticket_id to fetch one thread'), which implies the default list behavior. However, it says nothing about when to prefer this over reply_to_support_request or submit_support_request, and the status filter's intended use is never explained.

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