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

Annotations already mark this destructive and idempotent, but the description adds substantial context beyond them: the authentication requirement, the permission/ownership model, the cascade to history and comments, and the set of pages that cannot be deleted. This is exactly the behavioral detail an agent needs before invoking a destructive operation.

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?

Three dense sentences, each doing distinct work: what is deleted (with cascade), what credentials/permissions are needed, and what cannot be deleted. Front-loaded with the action and its effect; no filler.

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 one-parameter tool with no output schema and annotations that only give the safety profile, the description supplies everything an agent needs: auth requirement, permission rules, cascade behavior, and prohibited targets. Nothing material is missing.

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?

There is a single parameter with 100% schema description coverage ('The page's whole path'), so the schema carries the semantics. The description adds no further detail about the path format or identifiers, making the baseline 3 appropriate.

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 (delete) and resource (an article/page), and adds scope that the name alone doesn't convey: the page's history and comments go with it. This clearly distinguishes it from edit_page and restore_revision.

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 spells out the conditions for use: a ROLA bearer token is required, the author may delete, and on a shared ideas board anyone meeting the edit bar may delete. It also gives explicit exclusions (locked pages, hub articles, homepage). It stops short of naming an alternative tool for cases where deletion isn't allowed.

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