Delete Archived Test Cases

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds context by specifying the permanence and scope ('permanently delete all archived/deleted test cases'). It does not contradict annotations. However, it could warn about the lack of recovery or mention that the confirm parameter safeguards the action.

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 a single, well-structured sentence that front-loads the core action. No unnecessary words or information, making it highly concise.

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 simple destructive bulk action, annotations (destructiveHint), input schema, and presence of an output schema, the description covers the essential behavioral and usage context. No gaps are apparent for this tool's complexity.

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 adds no additional explanation for parameters. The schema already defines confirm, project_id, and output_format with descriptions. Baseline 3 is appropriate as the description does not enrich parameter understanding.

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 tool permanently deletes all archived/deleted test cases within the current project. It uses a specific verb ('delete') and resource, distinguishing it from siblings like delete_test_case (single) or delete_archived_shared_steps.

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 guidance is provided on when to use this tool versus alternatives. It does not mention that this is for bulk cleanup of archived items, nor does it exclude scenarios where delete_test_case is more appropriate. Sibling tools exist for single deletion, but no comparison is given.

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