remove_cases_from_collection

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the baseline burden is lower. The description adds a meaningful behavioral detail not present in annotations: it also deletes step results for those executions. This gives the agent a clearer picture of the destructive side effects.

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 two short sentences with no redundant filler. The primary action is front-loaded, and the extra destructive detail is isolated in the second sentence. Every word earns its place.

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 two-parameter mutation tool with strong schema coverage and annotations, the description covers the main action and an important side effect. It does not explicitly clarify that the test cases themselves are not deleted from the project, only removed from the collection, but the phrase 'from a test collection' strongly implies this.

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 100%, so both collectionId and caseIds are already documented with types and examples. The description adds no parameter-specific semantics beyond their role in the removal operation. This is adequate because the schema carries the parameter detail.

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 uses a specific verb and resource: 'remove test cases from a test collection.' This clearly differentiates it from siblings like add_cases_to_collection, and the phrase 'from a test collection' distinguishes it from delete_test_case. The additional side-effect sentence reinforces the exact scope.

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 no guidance on when to use this tool versus alternatives. It does not mention that add_cases_to_collection is the inverse or that delete_test_case has a different meaning. The usage context is implied by the name and description but never explicitly stated.

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