confluence_deleteSpaceTemplate

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

Annotations already set destructiveHint=true, but description adds critical context: the need for human approval, the confirm parameter constraint, and the lack of trash restore. Does not contradict annotations.

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?

Description is concise (3 sentences) and front-loads the key point (DESTRUCTIVE, human approval). Some redundancy in repeating the confirm requirement across sentences, but overall efficient.

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 5 params, no output schema, and annotations, the description covers essential behavioral traits and usage constraints. Lacks detail on return value or error cases, but sufficient for agent decision-making.

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%, but description adds meaning to 'confirm' (must be literal 'DELETE', not just boolean) and 'confirmName' (exact template name from listSpaceTemplates). Enhances understanding beyond schema descriptions.

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 deletes one space template, using a specific API endpoint, and distinguishes itself from sibling tools like 'confluence_deleteSpaceTemplates' (plural). The verb 'delete' and resource 'space template' are explicit.

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?

Provides explicit guidance: always stop and get human approval, never invent confirm, requires confirm='DELETE' and confirmName=exact template name. Also warns about no trash restore and advises archiving first. Clearly states when and how to use.

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