list_tickets

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the 'Read-only' sentence is mostly redundant. The high-value addition is disclosing that results come from a 30-ticket sample rather than the full queue — a real behavioral limitation an agent must know before concluding a ticket doesn't exist.

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?

Three short declarative sentences, front-loaded with the operation and the caveat that most affects interpretation. Nothing wasted.

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 single-parameter read tool with annotations covering safety, the description supplies the one thing structured fields cannot: the sample-size limitation. Return shape and count aren't described, but there is no output schema and the tool is simple enough that this is a minor gap.

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 0%, so the description should carry the parameter load. It mentions the default of open tickets, but that already appears in the schema's default field, and the closed/all enum values are never explained. Marginal value over the structured 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?

States a specific verb and resource ('List tickets') and adds a meaningful scope qualifier: it draws from a 30-ticket sample, not the full queue. No sibling tool is named, so differentiation from get_ticket_context is left to inference, but the operation itself is unambiguous.

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 implies when the tool applies by noting the sample size and the default to open tickets, but it never says when to prefer get_ticket_context or what to do if the ticket in question is not in the sample. Usage is suggested rather than stated.

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