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

Annotations already declare destructiveHint and non-readOnly, and the description adds substantial context beyond them: no soft-delete exists, the cascade deletes all test cases and their results, test runs survive but lose their suite link, and the refusal-then-force flow with returned counts. This is exactly the mutation detail an agent needs before invoking.

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 sentences, each carrying distinct payload: the irreversibility warning is front-loaded in capitals, followed by cascade consequences, then the force gate. No filler and no repetition of the annotations or schema.

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 destructive two-parameter tool with no output schema, the description covers destruction scope, side effects on related entities, the failure mode, and the escalation path. Even the returned counts are mentioned, so nothing an agent needs to call this safely 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?

Schema coverage is 100%, so both parameters are documented in structured form and the baseline would be 3. The description adds operational meaning over the schema by framing force as the release valve for a non-empty suite and prescribing a human-confirmation workflow, though it does not describe testSuiteId beyond what the schema says.

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 and resource ('PERMANENTLY delete a test suite') with an explicit scope qualifier (hard delete, no restore). This immediately distinguishes it from update_test_suite and from the restore_* family of siblings, so an agent need not open a schema to know what it does.

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?

Gives a clear precondition: a non-empty suite refuses unless force: true is passed, and force requires explicit human confirmation with counts relayed back first. It does not explicitly name a sibling alternative (e.g., delete_test_case for partial cleanup), so it falls short of a full when/when-not routing statement.

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