delete_page

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly communicates that the action is destructive and irreversible ('Permanently delete'), cascading ('all its descendants'), and gated on user confirmation. It could additionally mention permission requirements or effects on related content, but the core safety-critical behavior is well disclosed.

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 three short sentences with no filler. The primary action is front-loaded, followed by essential scope and safety constraints. Every sentence adds necessary information for correct and safe invocation.

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 destructive tool with no output schema, the description covers the essential invocation constraints: permanence, descendant scope, homepage restriction, and mandatory user confirmation. It does not describe error cases or return values, but those are less critical given the simplicity of the operation and the safety emphasis already 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%, and the single parameter 'pageId' is already described as 'Page id to delete.' The tool description adds no further meaning about the parameter, such as format, requiredness, or valid page types. Baseline 3 is appropriate since the schema carries the parameter documentation.

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 ('Permanently delete'), a clear resource ('a page'), and an important scope boundary ('all its descendants'). It also differentiates itself from sibling deletion tools like delete_model, delete_record, and delete_page_type by focusing on the page resource and adding the homepage restriction.

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 gives an explicit when-to-use condition: 'Only call after the user explicitly confirms.' It also provides a clear when-not-to-use constraint: 'Cannot delete the homepage.' This is strong practical guidance for an agent deciding whether invocation is appropriate.

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