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

Annotations already declare readOnly, idempotent, non-destructive, non-openWorld, so safety is covered. The description adds real value beyond them by disclosing what the response contains — the full comment thread and attachments — which tells the agent the call may be heavier than a plain record fetch.

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 with no filler; the scope of the returned payload is stated immediately after the lookup verb.

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 single-parameter read with complete annotations and no output schema, the description covers both what it fetches and what comes back (comments, attachments). Nothing critical is missing, though it does not mention error behavior for an invalid 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?

Only one parameter (ticket_id) at 0% schema description coverage, but the name is self-explanatory and 'by id' in the description confirms its role. The description adds no format, type, or example detail beyond the 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?

Specific verb ('Fetch') plus resource ('one support ticket') plus explicit scope ('by id, including its full comment thread and attachments'). The word 'one' clearly distinguishes it from the sibling list_support_tickets without needing the schema.

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 ... by id' suggests a single-record lookup versus list_support_tickets, but no explicit when-to-use or when-not-to-use guidance is given. An agent can infer the routing but must do the work itself.

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