superops_technicians_list

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions filters but does not describe pagination (cursor), default behavior (activeOnly defaults to true), or what the response looks like. Schema provides some parameter context, but the description adds little behavioral insight.

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 that front-loads the main purpose. No wasted words, but could benefit from additional structure to include key behavioral 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?

For a list tool with 4 parameters and no output schema, the description is minimal. It does not cover pagination behavior, default filter implications, maximum results limit, or what fields are returned. Schema fills some gaps, but the description is insufficient for full agent understanding.

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 baseline is 3. The description adds 'Can filter by active status or team,' which aligns with the activeOnly and teamId parameters but does not add new meaning beyond the schema descriptions.

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 it lists technicians (agents) in SuperOps.ai and mentions filtering by active status or team. This differentiates it from siblings like superops_technicians_get (single) and superops_technicians_groups (groups), but does not explicitly contrast with all siblings.

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 usage for listing with optional filters, but does not provide explicit guidance on when to use this tool versus alternatives like superops_technicians_get (for single) or superops_technicians_groups. No when-not-to-use advice is given.

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