Delete Page

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

Annotations already mark destructiveHint and idempotentHint. The description adds meaningful behavioral context: default trash behavior, the two-step workflow for purging, and the 400 error on invalid purge. This goes well beyond the structured hints and helps the agent predict outcomes.

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 compact: three sentences plus a small Args list. Front-loaded with the primary action, then the nuanced purge workflow, with no filler. Every sentence earns its place.

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 two-step state dependency, the description fully covers behavior, parameters, workflow, and failure modes. With no output schema, it appropriately focuses on inputs and side effects. It is complete and self-sufficient.

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 fully explain parameters. It does: page_id is 'ID of the page to delete' and purge is explained with its effect and precondition. It even notes the 400 error case, giving the agent the reasoning needed to avoid misuse.

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 opens with 'Delete a page (moves to trash by default)', a specific verb+resource statement that clearly distinguishes it from sibling delete tools like delete_blogpost or delete_attachment. It also clarifies the default trash behavior, which adds precision beyond the title.

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 gives explicit guidance for permanent deletion: 'first call delete_page to trash the page, then call delete_page again with purge=True'. It also states the precondition for purge (must already be in trash) and the error condition (400 on current page). It doesn't name alternatives, but for a delete tool with no close resource-overlapping siblings, this is sufficient context.

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