delete_page

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the confirmDelete safety gate, which is genuine behavioral information beyond the schema's boolean type, but it never states whether deletion is irreversible, what happens to child nodes, or whether undo can revert it.

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?

Two short sentences with the constraint front-loaded after the action. No filler, and the mandatory flag is surfaced before the agent reads the schema.

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 tool with no annotations and no output schema, the definition covers the action and the confirmation flag but omits reversibility, side effects on child content, and failure modes. Adequate to invoke, thin on consequence.

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%, so the description must compensate for two bare parameters. It explains confirmDelete's required value, adding real meaning, but pageId is left as an unexplained string with no mention of format, source, or how to obtain it.

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 ('Delete a page'), and names the identifier parameter, so the action is unambiguous. It does not differentiate itself from adjacent destructive siblings such as delete_node, delete_multiple_nodes, or delete_variable, which is the only real gap.

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 implicitly conveys a prerequisite ('Requires confirmDelete=true'), which tells the agent it cannot be called casually. However, it offers no when-to-use context relative to alternatives like delete_node or undo, and no guidance on whether deletion is recoverable.

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