list_ticket_replies

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that this is the paginated version, which is useful behavioral context beyond annotations, though it doesn't explain how pagination works (e.g., cursor or 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 sentences with the action front-loaded and no wasted words. The parenthetical adds necessary distinction without bloat.

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 tool is simple (one parameter, read-only), but the description does not clarify the pagination mechanism or the return format. Since there is no output schema, an agent cannot know how to handle pagination responses or whether all replies are returned in one call. This leaves a meaningful gap for a 'paginated version' 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?

The only parameter, ticket_id, is self-explanatory from its name, and schema description coverage is 0%. The description does not add any additional meaning about the parameter, but since it's the sole required field and clearly named, the gap is minor.

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 every reply on a ticket' and differentiates from get_ticket by noting it's the paginated version. This is clear and distinguishes it from siblings like get_ticket and reply_to_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 says when to use this over the alternative: it includes the same data as get_ticket's 'replies' field but is for long conversations requiring pagination. This gives a clear condition and names the sibling tool.

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