List ticket comments

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful content-level context by disclosing the fields returned (author, date, internal flag, text), but says nothing about pagination behavior, ordering, or the significance of the internal flag.

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?

A single tight sentence that front-loads the resource and lists the salient returned fields without waste. It is appropriately sized for a simple read tool.

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 list tool with rich annotations and 100% schema coverage, no output schema is needed and the description adequately conveys what comes back. It could be stronger by noting pagination (the schema exposes page/itemsInPage) or the meaning of the internal flag, but it is broadly complete.

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 full, page, ticketId, and itemsInPage are all documented in the schema, including defaults and max values. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 names the resource (a ticket's conversation) and enumerates the returned fields (author, date, internal flag, text), which clearly identifies it as a comment-listing tool distinct from siblings like list_ticket_attachments. It lacks an explicit verb, relying on the title, and doesn't explicitly differentiate from get_ticket, but the purpose is 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?

There is no when-to-use guidance, no mention of prerequisites (a valid ticketId), and no reference to alternative tools such as get_ticket or list_ticket_attachments. The agent must infer usage from the name alone.

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