superops_tickets_list

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

No annotations exist, so the description must carry behavioral disclosure. It states 'list' implying read-only, but does not explicitly confirm non-destructiveness, rate limits, or pagination behavior beyond the schema's cursor parameter. The description is minimally adequate for a list operation.

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, front-loaded sentence that conveys the core purpose and key filter options without redundancy. Every word earns its place, and it avoids repeating schema details.

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?

Given the tool has 7 optional parameters and no output schema or annotations, the description is minimal. It covers the resource and filters but omits details about default behavior, ordering, return format, or pagination. This is sufficient for a simple list tool but leaves gaps for an agent to understand all nuances.

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 coverage is 100%, so the schema already documents all parameters. The description adds a high-level grouping of filterable fields, which provides context but does not add significant meaning beyond what the schema offers. Baseline of 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 the tool lists tickets in SuperOps.ai and enumerates filterable fields (status, priority, client, assignee). This distinguishes it from sibling tools like superops_tickets_get (single ticket) and superops_tickets_create, using a specific verb and resource.

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 to use this tool (listing tickets with optional filters) but does not provide explicit when-not-to-use guidance or contrast with other list/sibling tools. No alternatives are mentioned, and there is no statement about prerequisites or preferred use cases.

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