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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds value by disclosing that the tool 'Returns summary info only' and supports pagination/filtering. This goes beyond the structured fields and helps set expectations about the response, though it doesn't cover potential rate limits or auth details.

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 first sentence is front-loaded and clear, but the description is bloated by duplication: the main block and the 'When to use' section are identical, and the parameter list repeats schema contents. While well-structured, not every sentence earns its place, making it less concise than it could be.

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 tool has no output schema, but the description explicitly addresses what is returned ('summary info only') and directs users to get_ticket for full details. All parameters, including defaults and filtering options, are covered. For a read-only list tool with rich annotations, the description is complete enough to guide correct use.

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%, so the input schema already fully documents all four parameters. The description's 'Parameters to validate before calling' section simply repeats the schema descriptions verbatim, adding no new semantic information. Baseline 3 is appropriate.

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 it 'Get[s] open support tickets' with pagination and search, using a specific verb and resource. It distinguishes itself from sibling tools by saying 'Returns summary info only — use get_ticket with the case number to get full ticket details', and the word 'open' differentiates it from fetch_closed_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?

The description provides clear context for when to use this tool (for summary listing of open tickets) and explicitly points to get_ticket as an alternative for full details. However, it doesn't give an explicit 'when not to use' statement or mention fetch_closed_tickets, so it slightly misses the bar for a 5.

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