Read the whole thread of a ticket

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

The description adds helpful context beyond the readOnlyHint annotation, such as message visibility categories and the presence of automated private notes. However, it states 'Every message on a ticket' while the schema's limit parameter (default 30) implies only the most recent subset is returned, creating a potential overstatement of behavior.

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 well-structured with a clear front-loaded statement, a bulleted list for message types, and two concise caveats. Each sentence adds value without redundancy, making it easy to scan and understand.

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?

The description thoroughly explains the semantic content of the response (message types, ordering, visibility) and important caveats about ticket description and automated notes. It lacks explicit mention of the limit/truncation behavior, but the schema provides that detail, so overall it is sufficiently complete for a read-only tool.

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 only 33%, and the tool description does not explain the parameters. ticket_id, limit, and max_chars_per_message are not described beyond their names and schema constraints, so the description fails to compensate for the low coverage.

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 reads the full ticket thread, lists messages oldest first, and labels each by author and visibility. It also distinguishes itself from freshdesk_get_ticket by noting the ticket description is fetched separately, making the purpose unambiguous.

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 context for use ('before drafting from this') and explicitly directs users to freshdesk_get_ticket for the ticket description, which is a relevant alternative. It does not enumerate all sibling tools or exclusions, but the main decision point is covered.

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