add_results_for_cases

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

No annotations are provided, so the description carries the full burden. It states the action ('Add') but doesn't disclose behavioral traits such as permissions required, whether this is idempotent, what happens on invalid inputs, or the format of the response. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that front-loads the key action and scope ('Add multiple test results for cases in a run') with zero waste. It's appropriately sized for the tool's complexity, making it easy for an agent to parse quickly.

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's complexity (a mutation with nested array parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like error handling, response format, or usage context, which are critical for an agent to invoke it correctly without additional signals.

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%, with clear descriptions for 'run_id' and 'results', so the schema does the heavy lifting. The description adds minimal value by implying that results are added to cases within a run, but it doesn't explain the semantics of 'status_id' or 'comment' beyond what the schema provides. Baseline 3 is appropriate given high schema coverage.

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 ('Add multiple test results') and the target ('for cases in a run'), which is specific and distinguishes it from singular result tools like 'add_result' or 'add_result_for_case'. However, it doesn't explicitly differentiate from 'add_results' (which might add results without case context) or 'add_results_for_run', leaving some sibling ambiguity.

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 provided on when to use this tool versus alternatives like 'add_result', 'add_result_for_case', or 'add_results'. The description implies bulk operations for cases within a specific run, but it doesn't state prerequisites, exclusions, or contextual constraints, leaving the agent to infer usage from the name and schema alone.

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