confluence_deleteSpaceTemplates

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

Annotations already include destructiveHint:true, idempotentHint:true. The description adds crucial behavioral details not in annotations: it starts with 'DESTRUCTIVE', requires human approval, details the confirmation mechanism, notes continuation on errors, and recommends an archive dump. No contradictions.

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 very concise (five sentences) with no wasted words. It is front-loaded with 'DESTRUCTIVE' to immediately signal danger. Each sentence conveys essential information: action, approval requirement, confirmation mechanics, error behavior, and precaution.

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 no output schema, the description covers the key aspects: destructive nature, human approval, parameter specifics, error handling, and a precaution (archive dump). It lacks return value description but that is not expected without output schema. Adequate for safe invocation.

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 baseline is 3. The description adds value beyond schema by explaining that confirm must be the exact string 'DELETE' (not true/yes), and confirmNames must match templateIds in order and be exact names. This clarifies parameter semantics.

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 action (delete), the resource (space Create templates), and the scope (several by id). It effectively distinguishes from siblings like 'deleteSpaceTemplate' (singular) and other space template operations.

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 provides explicit guidance: it requires human approval, specifies confirmation parameters (confirm='DELETE', confirmNames), and mentions error handling (continues on per-item errors). However, it does not explicitly compare to alternatives like the singular delete tool.

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