ninja_list_technicians

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

The description does not disclose behavior beyond the basic action, such as pagination handling, output structure, or any filtering limitations. Without annotations, this is insufficient for an agent to understand the tool's runtime behavior.

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 extremely concise with a single phrase, avoiding unnecessary words. However, it could be slightly expanded to include pagination hints without sacrificing conciseness.

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 simple list tool, the description is minimally complete, but lacks details on output format and pagination behavior. Given the absence of output schema, more context would be beneficial.

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?

The schema already describes the parameters with 100% coverage, so the description adds no extra semantic value. Baseline 3 is appropriate as the description neither enriches nor detracts from parameter understanding.

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 action 'list' and the resource 'technician accounts', making the tool's purpose unambiguous. It is distinct from the sibling tool ninja_get_technician which fetches a single technician.

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 usage guidelines are provided. The description does not differentiate this tool from other list tools or indicate when to use it versus fetching a single technician, leaving the agent without decision context.

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