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

Annotations already declare readOnlyHint=true, and the description's 'Read-only' is consistent (mild redundancy, not a contradiction). It adds genuine behavioral nuance beyond the annotations: a closed_since/closed_before window or a resolution filter already reaches closed tickets, so include_closed is only needed without one — a non-obvious interaction an agent would otherwise get wrong.

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?

Sized well and front-loaded — purpose, return fields, use cases, the include_closed caveat, then the filter list. The trailing filter enumeration partly duplicates the schema and could be dropped, but every earlier sentence carries informational weight.

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, the description correctly enumerates returned fields (number, title, kind, status, priority, assignee, cluster, plan state, resolution, timestamps) and covers filter interactions. It omits the limit/pagination default and result ordering, which the schema only partly covers, so it is strong but not exhaustive.

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 100%, so the baseline is 3, but the description adds real semantics: it enumerates the filter set and explains that narrowing to claimed fixes uses resolution='fixed' and that closed_since is the right entry point for resolved work. This goes beyond the per-field schema text.

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) plus the exact resource — the organisation's AI work board tickets — and characterizes the queue as the shared place where agents and humans collaborate on incidents, insights, gaps, automations, and requests. That framing cleanly separates it from siblings like ticket_get (single ticket) or list_support_tickets (support queue).

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?

Gives explicit use contexts ('see what work exists, what needs a human, what you are assigned, and what the team resolved in a given window') and even a worked example for resolved work (closed_since='24h' plus resolution='fixed'). It never names a competing sibling to prefer instead, so it stops short of full alternative routing.

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