delete_test_case

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

The description discloses key behavioral traits: 'permanently delete' indicates destructive action, clarifies version-specific behavior, and mentions the return code 204. With no annotations provided, it carries the full burden and does so adequately, though it could add more details like authorization requirements.

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 concise sentences with no unnecessary words. Critical information is front-loaded: the action, the target, the conditional behavior, and the return value. Every sentence 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?

Given the tool's simplicity (no output schema, two parameters), the description covers the return value (204) and the effect on test case versions. It is sufficiently complete for its complexity, though it could benefit from mentioning that the id can be either a string or number (but schema already covers that).

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% and the description does not add extra meaning beyond the schema's property descriptions. For a simple two-parameter tool, this meets the baseline but does not elevate it.

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 'Permanently delete a specific version of a test case' with the specific verb 'delete' and resource 'test case version'. It also explains the behavior when it's the only version, distinguishing it from sibling tools like delete_test_cycle or delete_test_plan.

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 explicit guidance on when to use this tool versus alternatives. Does not mention prerequisites, such as how to obtain the version number, or indicate that deletion is irreversible and should be used with caution.

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