Delete Confluence page

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description reinforces destructiveness and adds that the operation may delete or archive depending on server API and permissions, but it omits irreversibility, child-page impact, and required permission details.

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?

It is two short sentences with the destructive warning front-loaded. The second sentence is concise, though it partly repeats what the annotations already state.

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 mutation tool with one undocumented parameter and no output schema, the description is thin. It should clarify what is destroyed, whether descendant pages are affected, and what conditions trigger delete versus archive.

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?

The sole parameter, contentId, is not mentioned in the description, and schema description coverage is 0%. The agent gets no added meaning about what ID is required or what content types are acceptable.

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 states a specific verb and resource: delete or archive a Confluence content item. It is clear enough to distinguish this from read-oriented siblings, though it says 'content item' rather than matching the page-specific title and sibling set.

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?

It does not explain when to use this tool versus alternatives such as updating or archiving through another path. The phrase 'according to the server's REST API and permissions' hints at preconditions but gives no actionable guidance.

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