delete_page_rule

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

The description adds details beyond annotations: it explains the destructive nature (matches destructiveHint=true) and the human-approval gate, clarifying that without confirm it's a preview. This provides essential behavioral transparency.

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 sentences: first states purpose, second explains the key behavioral constraint. No unnecessary words. 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?

With a clean schema and clear description, all needed information is provided. The preview behavior compensates for the lack of an output schema, and the safety gate is well documented.

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?

The schema has 100% coverage, but the description adds meaning for each parameter. Zone_id is described as '32-char hex' with a hint to get it from list_zones. Rule_id is described as coming from list_page_rules. Confirm parameter is fully explained, including its role as a human-approval gate and preview behavior.

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 clearly states 'Delete a page rule by ID,' specifying both the action (delete) and the resource (page rule). This distinguishes it from sibling tools like delete_dns_record or delete_access_rule.

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 explains that confirm:true is required for actual deletion and that without it a preview is returned. It implies when to use the tool (for deletion) and the safety gate. It does not explicitly mention alternatives or when not to use, but the context is clear.

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