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

Annotations already establish the safe-read profile (readOnly, idempotent, non-destructive), and the description still adds real behavior: the 10-comment cap, that next offsets are returned for pagination, that text offsets count Unicode codepoints while commentOffset counts comments, and that bodies are boundary-marked untrusted content. The untrusted-content warning in particular is safety context an agent cannot get from annotations or schema.

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?

Dense single paragraph with the core fetch statement front-loaded and no filler sentences; each clause (offsets, untrusted content, get_report handoff) adds distinct value. It is on the long side, and the parameter guidance could be broken out more scannably.

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 and 0% schema coverage, the description carries the return-shape burden and does so by enumerating fields and pagination offsets, plus the security caveat. It does not describe error/empty cases or what the boundary marker format looks like, leaving minor gaps for a tool of 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?

Schema description coverage is 0%, so the description must carry all six parameters — and it largely does, disambiguating the three offset parameters, naming the max-10 limit, and explaining the codepoint-vs-comment counting rule. It stops short of stating defaults or the exact boundary-marker/return shape per parameter, so a small amount is still left to inference.

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?

Specific verb+resource ('Fetch one board card (ticket)') followed by an enumeration of exactly what is returned: title, number, column, assignee, description, comments with ids/authors, linked event ids. This clearly separates it from siblings like search, get_ticket_options, get_ticket_attachment, and update_ticket.

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?

Explicitly routes the agent to the right parameters (commentOffset/commentLimit for the thread, descriptionOffset for long descriptions, commentBodyOffset with commentLimit:1 for long comments) and hands off to get_report via a returned eventId. It notes where projectId/cardId come from, but gives no explicit 'when not to use this' or a named alternative for fetching a ticket another way.

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