delete_page_rule_tool

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

With no annotations provided, the description must disclose behavior on its own. It only states 'Delete a page rule' without indicating that this is a destructive, irreversible operation, any permission requirements, or what happens on success/failure. For a delete tool, this is a critical omission.

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 a single sentence with no superfluous words. It is concise and front-loaded, accurately stating the core function. There is zero waste, which is ideal for a simple operation.

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?

Given the tool is a delete operation with no annotations and a minimal description, it lacks essential context. It does not mention that the operation is permanent, that the zone and rule must exist, or what the output schema contains. The existence of an output schema does not compensate for the missing behavioral and prerequisite context.

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 input schema covers 100% of parameters with descriptions ('Page rule ID (32-character hex string)' and 'Zone ID (32-character hex string)'). The tool description adds no additional parameter context, such as how to find these IDs or any dependencies between them. Since schema coverage is high, a baseline of 3 is 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 clearly states the tool's action: 'Delete a page rule.' This is a specific verb and resource, directly distinguishing it from sibling tools like create_page_rule, update_page_rule, and list_page_rules. It accurately conveys what the tool does without ambiguity.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., that the page rule must exist or how to obtain the rule_id), nor does it contrast with similar delete operations like delete_waf_rule. The name and siblings imply usage, but the description itself lacks explicit guidance.

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