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

Annotations already mark it readOnly, idempotent, and non-destructive; the description adds substantial behavior beyond that: newest-first ordering with legacy null times last, cursor binding and 24-hour expiry, fresh-read behavior when omitting cursor, and the caveat that this is 'not completion evidence or permission to act.' It also states the required tickets:read permission.

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?

The description is dense but every sentence earns its place: purpose, ordering, pagination, cursor lifespan, semantic warning, and permission. It is front-loaded with the core purpose before moving to details.

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 an output schema present, the description doesn't need to explain return fields. It covers pagination semantics, cursor lifecycle, archive scope, ordering edge case, permission requirement, and a critical semantic boundary. Nothing an agent needs to call or interpret this tool correctly is missing.

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%, but the description compensates well for limit and cursor: it explains the 1–100 range, default of 50, next_cursor/has_more/reached_oldest semantics, and fresh-read behavior. ticket_id is not elaborated in prose, but the schema already specifies it as a required UUID, so the missing prose is not a meaningful gap.

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?

Description opens with a specific verb and resource: 'Read complete discussion bodies, authors, kinds and timestamps for one owned ticket.' It clearly defines scope (one owned ticket, including archived tickets) and distinguishes the tool as the read-oriented comments resource among ticket siblings like ticket_comment and ticket_get.

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?

Provides clear context on when this tool applies: reading comments for an owned ticket, including archived tickets, with pagination instructions. It doesn't explicitly name an alternative tool to use instead, but the read-only nature and 'one owned ticket' constraint give sufficient selection guidance.

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