Get ticket conversation

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

The description adds significant behavioral detail beyond the readOnlyHint/destructiveHint annotations. It explicitly states that HTML is stripped, making the conversation 'readable', and that private staff notes are included. This informs the agent about content and format, which is not implied by the annotations alone.

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 a single, front-loaded sentence that conveys the core purpose and key behavioral traits without any filler. Every phrase adds value (message thread, HTML stripped, readable, private staff notes).

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?

For a read-only tool with a straightforward purpose, the description covers the essential information: what is fetched, the transformation applied, and the inclusion of private notes. It does not explicitly mention pagination behavior or response format, but the schema handles pagination parameters, and the absence of an output schema is acceptable given the tool's simplicity.

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 input schema covers all three parameters with descriptions for each (ticket_id, limit, offset), giving 100% coverage. The description adds no parameter-specific meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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?

The description clearly states the tool's function: 'Get the message thread of a ticket' with a specific verb and resource. It also distinguishes from siblings like get_ticket by noting HTML is stripped and that it includes private staff notes, making it unique among ticket-related tools.

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?

The description provides clear context: it is for reading a ticket's conversation thread, including non-public staff notes. It does not explicitly name alternatives or state when NOT to use it, but the naming and description make the use case obvious relative to siblings like reply_ticket or update_ticket.

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