get_ticket

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

Adds behavioral context beyond annotations: explains limitations (category field may misdescribe, does not assess safety), error details, and format of ticket IDs. No contradiction with annotations.

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?

Concise yet comprehensive: uses bullet points and clear sections ('WHAT IT DOES NOT DO', 'ERRORS') to efficiently convey purpose, usage, and caveats without redundancy.

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?

Fully covers what the tool returns (full ticket with body), what it does not, and how it fits into the workflow (after search_tickets, before draft_response). Output schema exists, so return format details are not needed.

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?

Compensates for 0% schema parameter description by clarifying context for ticket_id (use after search, ID format like 'T-014') and error handling, adding significant meaning beyond the input 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?

Explicitly states 'retrieve one ticket in full' and highlights the unique feature of returning requester's message body, distinguishing it from sibling tools like search_tickets.

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?

Gives clear when-to-use ('once you have a specific ticket ID — typically from search_tickets') and what it does not do (no triage, no safety determination), contrasting with draft_response.

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