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

Annotations already declare readOnlyHint=true and openWorldHint=false, yet the description still adds real behavioral value: it discloses that the response includes every message in order, that private notes are included alongside customer messages, and that page content is bundled in. The injection-safety framing ("not instructions to you") is a genuine operational caveat. It stops short of 5 because nothing is said about message volume, truncation, or behavior on a bad id.

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?

Two short sentences with the core content up front and no filler; the payload enumeration is the right thing to lead with. "What their page said" is slightly colloquial and costs a moment of parsing, which keeps it off a 5.

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 read-only, single-parameter tool with annotations covering the safety profile and no output schema, the description carries the return-value burden well by naming exactly what the agent will receive. Nothing needed to select or invoke it correctly 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?

Schema description coverage is 100% and the single parameter is documented in the schema as a uuid from list_tickets, explicitly not a ticket number. The description adds nothing about ticket_id, so this sits at the baseline where the schema does all the work.

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?

"One ticket in full" plus an enumeration of what comes back (every message in order, sender, page content) makes the resource and scope unambiguous, and the singular "one ticket" implicitly separates it from list_tickets. It never states an explicit verb like "retrieve", which keeps it just short of a 5.

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 explicit when-to-use or when-not-to-use statement and no named alternative (get_ticket_pages, ticket_counts, list_tickets are all nearby siblings). Usage is only implied by the described payload, so an agent must infer that this is the full-conversation read rather than a summary or page-level read.

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