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

With no annotations, the description carries the full burden. It usefully discloses the auth prerequisite ('Requires: token') and explains the meaning of the last_message_author value, which is real behavioral context. It stops short of pagination, ordering, or result-size behavior for a listing endpoint.

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 compact sentences front-load the resource and scope, followed by a terse prerequisite. Nothing is wasted, though the 'Requires: token' fragment is clipped enough to read as a note rather than prose.

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 no-parameter list tool with no output schema or annotations, the description covers the core return shape (status, last-message info, author semantics) and the auth requirement. Missing only pagination/result-count behavior, which is a minor gap at this complexity.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to clarify and it does not mislead about inputs. No additional parameter meaning is needed.

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 and resource ('List your support tickets') and previews the returned fields (status, last-message info), so the agent knows exactly what this retrieves. It does not explicitly distinguish itself from get_ticket, but list-vs-single-fetch is 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?

Usage is implied by the verb 'list' rather than stated: there is no guidance on when to use this instead of get_ticket, nor any mention of filtering or paging behavior. An agent can infer the use case, but nothing is made explicit.

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