gorelo_list_tickets

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

With no annotations, the description carries the behavioral burden and discloses useful traits: cursor-based pagination and default sort order (updatedOn desc). It does not mention response shape or rate limits, but for a read-only list endpoint the provided behavior is reasonably transparent.

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 one compact sentence that front-loads the core verb and resource, then immediately gives pagination, default sort, and the filter catalog. Every clause adds information and there is no filler.

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 17-parameter list tool with no output schema, the description covers the core purpose, pagination, default ordering, and nearly all filter dimensions in a compact form. It could add a note about return shape or referencing sibling list endpoints for IDs, but an agent has enough context to invoke it correctly.

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 only 59%, and the description compensates by summarizing filter categories that map to many sparsely documented ID parameters: status, client, priority, type, assignee, contact, tag, group, keyword, and date range. It leaves cursor, pageSize, and sort controls to the schema, which already documents them.

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 opens with a specific verb and resource: 'List tickets for the service provider.' It also adds pagination behavior and names the distinct list/filter operation, which separates it clearly from singular or metadata siblings like get_ticket and list_ticket_statuses.

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 makes the intended use clear: listing and filtering tickets with many available dimensions, plus the default sort order. It does not explicitly name gorelo_get_ticket as the single-ticket alternative, so it stops just short of full exclusionary guidance.

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