delete_case

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered. The description still adds value by disclosing that the deletion is permanent (irreversible, no trash/undo) and that the target is a whole case directory in the workspace, which destructiveHint alone does not convey. It stops short of stating whether anything else (jobs, logs) is touched or what is returned.

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?

A single front-loaded sentence that leads with the permanence qualifier and the resource, with no filler or redundancy.

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 two-parameter, destructive operation with full schema coverage and annotations carrying the safety hints, the critical missing piece an agent needs is irreversibility, which the word 'Permanently' supplies. Nothing further is mandatory, though it could note that confirm must be set and whether the deletion can be undone.

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 description coverage is 100%: the schema explains 'case' (name or absolute path inside an allowed root) and 'confirm' (must be true to actually delete). The description adds no syntax, format, or path-restriction detail beyond that, so the baseline 3 applies.

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 case directory') with the target scope ('from the workspace'), so the agent knows exactly what is affected. It does not distinguish itself from the sibling clean_case, which plausibly removes case artifacts while keeping the directory, leaving the boundary between the two implicit.

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?

There is no when-to-use guidance, no statement of prerequisites, and no mention of the obvious alternative clean_case for less aggressive removal. The adverb 'Permanently' hints at the condition under which this tool is appropriate, but the agent must infer it rather than being told.

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