get_tickets

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

The description adds behavioral transparency beyond the 'readOnlyHint' annotation by detailing cursor pagination, sort options, and per_page limitations. No contradictions with annotations.

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 concise sentences: first states purpose, second provides critical usage details. Front-loaded with no redundant information.

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 description covers core functionality (pagination, sort, limit) for a 4-parameter list tool. An output schema exists, so return values need not be described. Slight missing guidance on sort_order and when to use it versus search_tickets.

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?

With 0% schema description coverage, the description compensates by explaining cursor (pagination), sort_by (options), and per_page (max 100). However, it omits sort_order, which is a parameter. The explanation adds meaning but could be more complete.

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 'Fetch tickets with cursor pagination,' indicating a specific verb and resource. It differentiates from siblings like 'get_ticket' (single ticket) and 'search_tickets' (search with filters) by focusing on cursor-paginated listing.

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 explicit guidance on pagination: 'Pass the returned after_cursor as cursor to get the next page.' It also specifies sort_by options and per_page max. However, it does not explicitly distinguish when to use this tool versus sibling tools like 'search_tickets' for filtered queries.

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