Delete Page

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

The destructiveHint annotation already communicates that this is a destructive operation. The description adds only 'existing' to indicate the page must already exist, but it does not elaborate on consequences such as permanence, cascade deletion, or permission requirements. No contradiction with 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?

The description is a single, tightly scoped sentence with every word earning its place. It opens with the action verb and names the target resource without unnecessary detail.

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 one-parameter delete operation, the description combined with the destructive annotation and output schema is nearly complete. A brief note about irreversible effects or cascading deletion of child pages would improve it, but the essentials are present.

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 page_id parameter is fully described as the ID of the page to delete. The description provides no additional information about the parameter format, source, or special considerations, so it adds no value beyond the schema. 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?

The description states a specific verb and resource: 'Delete an existing Confluence page.' This is clearly distinct from sibling tools like create_page, update_page, and delete_attachment, so an agent can immediately understand what operation this tool performs.

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?

Usage context is implied by the name and description: use this tool when you want to delete a particular page. However, there is no explicit guidance about when not to use it or reference to alternatives such as confluence_delete_attachment for attachments.

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