add_cases_to_execution

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

Beyond the annotations, the description reveals important behaviors: invalid/cross-project case ids are skipped, an empty result creates no group, and the return value contains {added, skipped, groupId}. These details materially change how an agent interprets outcomes and help it detect partial failures.

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 compact and front-loaded: the core operation and object are stated first, followed by crucial constraints and the return shape. Every sentence earns its place, with no redundant repetition of schema fields.

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 mutation tool with no output schema, the description provides enough behavioral context: what is being added, the validity constraints, the empty-result edge case, and the return contract. The annotations already cover safety profile, so no critical guidance is missing.

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 already 100%, but the description adds relational meaning: caseIds must map to cases in the execution's project, the name labels a group, and invalid ids cause skips. This goes beyond the schema's basic type and format 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 the operation: add individual test cases to an execution as a named group, explicitly scoped to source_type cases. This distinguishes it from sibling tools like add_cases_to_collection and add_suites_to_execution without needing to open their schemas.

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 gives clear context: use this tool when adding case-level groups to an execution, and the source_type cases qualifier signals when it does not apply. It does not explicitly name alternatives such as add_suites_to_execution, but the intended usage is still easy to infer.

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