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

Annotations already flag this as non-read-only, destructive, and non-idempotent, so the bar is lower. The description still adds real value beyond them: it discloses that changes are reversible via cf_undo, that under_attack false restores the prior level, and that development_mode is a temporary 3-hour cache bypass.

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?

Purpose and mode behavior are front-loaded, and most clauses earn their place by naming values or clarifying shortcuts. The middle sentence is dense and slightly run-on, but there is no padding or redundancy.

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 9-param mutation tool with no output schema, the description covers modes, reversible undo, and the key settings. The main gap is that some parameters (min_tls_version, browser_check, automatic_https_rewrites) are listed without any value or effect explanation, and the read-mode return shape is unaddressed.

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 coverage is only 11% (just the zone param), so the description must compensate. It does supply enum values for security_level and ssl that the schema lacks, and groups settings by mode, but leaves min_tls_version values and the semantics of browser_check/automatic_https_rewrites unexplained, so compensation is partial.

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 pair (read or change) and resource (Cloudflare zone settings), then enumerates the exact settings involved. It is clearly distinguishable from siblings like cf_dns_add, cf_firewall_add, and cf_purge_cache, which target different Cloudflare resources.

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 implies the two modes (no args = read all; passing args = change) and routes undo to cf_undo, which is helpful. However, it never explicitly states when to use this tool versus other settings-adjacent siblings, nor any when-not-to-use conditions.

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