Get Ticket

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

The annotations already establish a non-mutating, open-world read. The description adds that the ticket must already exist and is retrieved by two keys, but provides no further context about access requirements, missing tickets, or other runtime behavior.

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?

The single sentence is direct, front-loaded, and free of filler. Its brevity is appropriate for a simple keyed retrieval operation.

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 input schema, annotations, and output schema supply most of the details needed to invoke this simple read correctly. The principal gap is sibling-selection guidance, especially differentiation from get_my_ticket and list_my_tickets.

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 description reinforces that account_code and ticket_id jointly identify the ticket, offering modest context for the otherwise undescribed ticket_id. The schema already documents account_code, lang, and currency, and the description adds no identifier sourcing or formatting details.

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 states a specific verb and resource and identifies the two lookup keys: account code and ticket id. It does not explicitly distinguish this operation from the closely related get_my_ticket or list_my_tickets siblings.

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?

Mentioning an existing ticket and both identifiers implies the intended lookup situation, but there is no explicit when-to-use guidance. In particular, it does not explain when get_my_ticket or list_my_tickets would be preferable.

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