Get a ticket

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so safety behavior is covered. The description adds genuinely new behavioral context about payload scope: it returns only the FIRST comment as the description and only the LAST end-user and technician comments, which prevents an agent from assuming it returns the full comment thread.

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?

It is a single front-loaded phrase with no filler; every clause enumerates concrete returned data. It is a fragment rather than a full sentence, but it is efficiently sized for the amount of information conveyed.

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?

Because there is no output schema, the description rightly explains the return payload, and it does so well. However, it leaves the includeRelations parameter undocumented and gives no hint of how this tool relates to the overlapping ticket-listing siblings, so it is only adequately complete for a two-parameter retrieval 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 coverage is 50%: ticketId is documented in the schema while includeRelations has no description anywhere, and the description mentions neither parameter. It does not compensate for the coverage gap, leaving the meaning of includeRelations (which controls whether related records are returned) entirely unexplained.

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 identifies the specific resource and enumerates its returned content (description/first comment, last end-user and technician comments, SLA dates and durations), so the agent knows exactly what a ticket record contains. It does not, however, differentiate from overlapping siblings such as list_ticket_comments or get_ticket_work_hours, which fetch subsets of the same data.

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 prerequisites, and no mention of alternatives. With siblings like list_tickets, list_ticket_comments, and get_ticket_work_hours available, the description never states why an agent should call get_ticket instead of those.

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