delete_test_case

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuinely new behavior beyond them: deletion is a soft delete (moved to trash) and is reversible. It does not mention permission requirements or side effects on linked test runs/results.

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 first two sentences say the same thing twice ('Delete a test case. Delete a test case using its unique identifier.'), wasting a sentence. The third sentence carries the only new information, so the structure is front-loaded but partially redundant.

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 single-parameter destructive tool with no output schema, the description covers what an agent most needs: the identifier to supply and the recoverable nature of the deletion. Missing only scope-of-impact details (permissions, effect on linked runs) and sibling routing.

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?

Only one parameter, and the schema already carries a description for testCaseId ('The test case identifier'). The description's 'using its unique identifier' restates that rather than adding format, type, or lookup guidance, so it neither compensates for the low coverage metric nor adds meaning.

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?

States a specific verb (delete) and resource (test case), and specifies the deletion key ('using its unique identifier'). It does not differentiate itself from the adjacent bulk/restore siblings such as post_batch_delete_test_cases or restore_test_case, but the core purpose is unambiguous.

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 when-to-use guidance or routing to alternatives. The mention that cases 'can be restored later' implicitly points at restore_test_case, but the tool is never named and no condition is given for choosing single vs. batch delete.

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