Get one ticket with its context

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond annotations: the description field is the original customer request converted from email HTML to markdown, not the latest message. This is meaningful behavioral context but stops short of richer detail like return format or pagination.

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 description is two short, focused paragraphs. The first states what the tool returns; the second clarifies a subtle point about the description field and gives a directional pointer to a sibling tool. No filler words or redundant repetition of schema information.

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?

For a simple read-only tool with one parameter and no output schema, the description is complete. It lists what detail is included, clarifies the meaning of the description field, and warns users not to mistake it for the latest message while directing them to the appropriate tool for the thread. The annotations cover safety aspects, so nothing essential is missing.

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 only parameter, ticket_id, is not explicitly described in the text. The schema already documents it clearly (required integer with range). The description's mention of 'single ticket' implies an ID is needed but doesn't explicitly map 'the ticket's ID to the ticket_id parameter. With 0% schema coverage in the description, a more explicit link would help, though the parameter's meaning is self-evident from the tool name and 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 description clearly states the tool retrieves 'Full detail for a single ticket' and enumerates specific content (fields, requester, company, reply timestamps). It also differentiates from siblings by noting the description is the original request, not the latest message, and explicitly names freshdesk_get_conversations as the alternative for the thread.

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?

The description gives explicit usage guidance: use this tool for full ticket detail, but if you need the thread/latest messages, use freshdesk_get_conversations instead. This directly addresses when-to-use vs. alternatives.

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