Delete a page

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description's only added signal is 'Permanently', which reinforces irreversibility. It says nothing about cascade effects (sharing, published links, child pages), permissions required, or whether the deletion is recoverable.

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?

A single short sentence with zero padding, and the destructive character is front-loaded in 'Permanently'. It is efficient, though its brevity borders on under-specification.

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?

The annotations carry the destructive/idempotent profile and there is no output schema to explain, so the safety essentials are present. However, for a destructive mutation with an undocumented required parameter, the description omits authorization needs, recovery options, and side effects on published or shared artifacts.

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 0%, and pageId carries no description in the schema. The description does not explain the identifier's format or where the agent obtains it, so it fails to compensate for the documentation gap on the single parameter.

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?

States a specific verb and resource ('Permanently remove a page'), and the word 'permanently' implicitly separates it from unpublish_page. It never names a sibling, so an agent must infer the boundary between deleting and unpublishing on its own.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as unpublish_page or update_page. The adverb 'permanently' hints at irreversibility but does not tell the agent when this tool is the right choice over its siblings.

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