Delete one test case

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

Annotations already mark the tool as destructive, but the description goes further by stating 'This cannot be undone,' which is crucial behavioral context for an agent deciding whether to invoke it. It also clarifies that the operation acts within a draft, adding scope beyond what annotations alone convey.

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?

Two compact sentences deliver the action, the resource scope, the ID source, and the irreversibility warning. Every sentence earns its place with no filler or redundancy.

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 delete operation with destructive annotations and an output schema, the description covers all essential context: what to delete, where the ID comes from, and that deletion is permanent. Nothing needed for correct invocation 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?

The schema already covers both parameters fully, so baseline is 3. The description adds value by directly telling the agent to source testcase_id from repovive_build_list_testcases and 'by its id,' reinforcing the link between the parameter and the list operation, which slightly exceeds bare 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 a specific action (delete) on a specific resource (one test case from a draft) and by a specific identifier (its id). It also references repovive_build_list_testcases, which distinguishes it from related test-case operations like clear_testcases or add_testcases.

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 explicitly instructs the agent where to obtain testcase IDs, providing a clear prerequisite for use. It does not explicitly contrast with alternatives such as clearing all test cases, but the target use case—deleting a single test case from a draft—is clear enough for selection.

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