delete_test_collection

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

The description adds value beyond the annotations. Although destructiveHint and idempotentHint already mark the operation as destructive and repeatable, the description clarifies the exact nature: it is an archive/soft delete, the collection is recoverable via UI, and test executions remain intact. This materially refines the meaning of the destructive hint and helps the agent avoid assuming irreversible deletion.

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?

Three short sentences deliver high-value information with no redundant words. The most important fact, 'soft delete', is front-loaded, and the following sentences add critical behavioral nuance about restoration and preserved executions.

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?

The description is complete for a simple one-parameter mutation. It explains the operation type, reversibility, and impact on test executions. There is no output schema, so the absence of return-format details is acceptable. The core behavior an agent needs to invoke this tool safely and correctly is fully covered.

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?

There is only one parameter and the schema description coverage is 100%. The schema already explains that collectionId is the test collection UUID to archive. The tool description does not add further parameter-specific detail, which is acceptable because the schema carries that burden.

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 specific operation: 'Archive (soft delete) a test collection'. It identifies both the verb and the resource, and explicitly clarifies it is a soft delete. This distinguishes it from the sibling delete_* tools, especially delete_test_case and delete_execution.

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 does not explicitly name alternative tools or state when not to use it, but it gives clear behavioral context: restoration via the UI and preservation of test executions. For an agent deciding whether to use this tool, the 'soft delete' framing and reversibility strongly imply this is the safer deletion pathway.

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