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

Annotations only declare readOnlyHint=true, and the description adds substantial context beyond that: the newest-first timeline ordering, the windowed/truncated body and plan returns, the body_total_chars disclosure, and the decision_request block on blocked tickets. It does not cover error behavior (invalid id, permissions), which keeps this short of a 5.

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?

Front-loads the what/why before the paging mechanics, and each sentence carries information. It is on the long side and partly restates schema text verbatim, but there is no filler or tautology.

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?

No output schema exists, so the description carries the full burden of describing the return: it enumerates the fields, explains windowing/truncation semantics for body, plan, and events, and calls out the decision_request case. An agent has enough to call it correctly and to page through results.

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 baseline is 3, but the description adds real meaning: it marks ticket_number as the preferred identifier and links each paging parameter to the output field that drives it (body_next_offset->body_offset, plan_document_next_offset->plan_offset, recent_events_next_before_sequence->events_before_sequence).

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+resource ('Get one AI work board ticket') and then enumerates the exact return payload (title, body, plan document, timeline, linked sessions/workspaces/insights), which cleanly separates it from ticket_list (multiple) and ticket_decide (answering). An agent can identify what this tool is without opening the schema.

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 when-to-use ('load your assignment context before working a ticket, or to check what colleagues said'), names the alternative tool for the decision case ('answer it with ticket_decide'), and states identifier preference ('ticket_number (preferred) or ticket_id'). Nothing is left to inference.

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