list_tickets

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

Annotations already declare readOnlyHint=true, so the description does not need to restate that. However, the description adds nothing beyond 'List tickets' – it does not explain openWorldHint (e.g., that results may be partial or require pagination) or mention any default behavior like sorting or limit. With annotations covering the read-only nature, the description contributes little extra behavioral context.

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 a single, concise sentence with no filler. It is appropriately short, though it could include a brief note on pagination or sorting to be more useful without becoming verbose.

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 list tool with four optional parameters and no output schema, the description is incomplete. It does not clarify how to use pagination effectively, which sort fields are valid, or whether the response is a paginated collection. The schema covers parameter definitions but not usage context. An agent would need to guess at the intended workflow.

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 all four parameters (page, sort_by, per_page, sort_order) are already documented in the schema. The description adds no additional meaning or usage hints; the baseline of 3 applies because the schema does the heavy lifting.

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 states the verb 'List' and the resource 'tickets' clearly, so the agent knows it fetches multiple tickets. However, it does not differentiate from siblings like get_ticket (singular) or export_tickets, and it lacks any scoping details such as filtering or which ticket fields are returned. It is not a tautology, but it is minimal.

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 guidance on when to use this tool versus alternatives. It does not mention that get_ticket is for a single ticket, nor does it advise on pagination or sort usage. An agent must infer that this is the general list operation, with no exclusions or context.

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