get_ticket

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description does add that the full body and comments are returned, which is useful payload context beyond the annotations, but it says nothing about error behavior for invalid or deleted tickets or any access constraints.

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 front-loaded sentence that answers what is returned. The '[policy: allow]' prefix is metadata noise that does not help an agent select or call the 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?

The tool is simple: one required parameter, an output schema that documents the return shape, and annotations covering safety. Return values need not be explained, so the remaining gap is only the lack of failure-mode guidance for a nonexistent ticket_id.

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 0%, so the description carries the burden, yet it adds no format or source information for ticket_id (prefix, numeric vs slug, where to obtain it). The parameter name is self-explanatory, which keeps this at a minimum-viable 3 rather than lower.

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 ('Get one ticket') plus the payload scope ('full body and comments'), which reads clearly as single-record retrieval versus the sibling search_tickets. It never names the sibling explicitly, so differentiation relies on the word 'one'.

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: 'one ticket' suggests fetching a known ticket_id rather than searching. There is no explicit when-to-use versus search_tickets, no mention of what happens if the ticket is missing, and no mention of related siblings like add_comment or update_ticket.

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