tickets_list_comments

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

Without annotations, the description still conveys the key behavioral fact: this is the endpoint that retrieves the full comment set beyond the 5 embedded on the case. It implicitly marks the operation as read-only ('List'), and the truncation caveat gives the agent meaningful expectations about what it returns.

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, each earning its place: the first states the action and resource; the second supplies the essential reason this tool exists. No filler or restatement of the schema.

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 is complete for a simple paginated list tool: output schema, full parameter docs, and the useful distinction from the case object's comment field are all present. An agent has enough to select and invoke it correctly without further investigation.

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 coverage is 100%, with each parameter already documented (ticket_id, limit, offset, fields), so the description need not add parameter details. The mention of 'the rest' lightly ties to limit/offset but adds no semantic value beyond 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?

The opening sentence uses a specific verb and resource ('List all comments on a case'), stating exactly what the tool returns. The second sentence distinguishes it from the case object's embedded comments ('latest 5'), so it is not confused with a case-fetching sibling.

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?

It gives a clear condition: the case object only carries the latest 5 comments, so use this tool for the remaining ones. It does not name the sibling tool explicitly (e.g., tickets_get_case), but the alternative and the deciding condition are identifiable.

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