superops_technicians_list

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

No annotations are present, so the description carries the full behavioral disclosure burden. It restates the filter options already represented in the schema and does not mention pagination behavior, output shape, or the read-only side-effect profile except by the verb 'list'.

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 short, front-loaded sentences with no filler. The core purpose comes first and the optional filter capability is stated compactly.

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 4-parameter paginated list with no output schema and no annotations, the input schema covers the call mechanics, but the agent is left to infer return shape, pagination details, and how this relates to superops_technicians_get and superops_technicians_groups. That is a moderate gap, not a fatal one.

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 max, cursor, teamId, and activeOnly are already documented with defaults. The description's 'active status or team' maps to two params but adds no meaning beyond the 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?

The description names a specific verb and resource: 'List technicians (agents) in SuperOps.ai'. The parenthetical clarifies domain terminology, and the second sentence adds filtering scope, making it easy to distinguish from the singular superops_technicians_get sibling.

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?

No guidance is given for when to choose this over superops_technicians_get or superops_technicians_groups. The phrase 'Can filter by active status or team' describes capabilities, not decision criteria or exclusions.

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