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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description doesn't need to re-establish safety. It adds real context beyond them: the result set is personal and filtered to unfinished/QA-pending work, and each entry includes body and evidence — useful for an agent deciding whether it has enough to act.

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 sentences, no filler. The content description comes first and the actionable 'call it first' instruction is placed at the end where it lands as the takeaway.

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 parameters and no output schema, the description carries the burden of explaining returns, and it does name the payload ('body and evidence'). It leaves the shape of the response (ordering, paging, item fields) implicit, but for a simple read-only listing that is a minor gap.

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. No parameter behavior is claimed or needed, and the description correctly offers no input guidance.

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 (list) and a precisely scoped resource: 'your unfinished tickets' plus 'tickets waiting for your QA review'. It also names what each item carries ('body and evidence'), which separates it from a detail-fetching sibling like get_ticket, though it doesn't explicitly contrast with any sibling by name.

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?

'Call it first when you start or are woken' gives an explicit ordering rule that an agent can act on, and the scoping to 'your' tickets implies other tools cover other people's tickets. It stops short of naming exclusions or the alternative to use when a specific ticket is already known.

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