List ticket conversations

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the ordering guarantee ('oldest first'), which is genuine behavior not in the annotations, but says nothing about pagination limits or total counts despite page/per_page parameters.

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?

Two short sentences, front-loaded with the action and scope, then the returned shape. Every clause carries information; nothing is wasted.

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 and annotations covering safety, the description needn't explain return values, and it still summarizes them usefully. The one remaining gap is paging behavior, which matters for a list tool that defaults to 30 records.

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 100%, so the baseline of 3 applies; the description adds no parameter detail at all. It never mentions that results are paged (default 30, max 100), leaving the agent to discover paging only from the schema.

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 and resource ('List the replies and notes on a ticket') plus ordering ('oldest first'), which is far more precise than the tautological name. It implicitly distinguishes itself from the ticket-level readers (get_tickets, get_ticket_by_id) and the conversation mutators, though it never names any sibling explicitly.

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?

Usage is only implied: an agent can infer this is the way to read a ticket's thread, but there is no statement of when to prefer it over list_ticket_activities or get_ticket_by_id, and no mention of pagination thresholds that would suggest fetching multiple pages.

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