Edit Cloudflare zone settings

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, but the description adds real operational detail beyond them: a read-before-write validation pass, refusal of no-op changes, plan-based rejections, and partial-application semantics ('If a later change fails, the result lists what was changed, the failure and the settings not sent'). The one small tension is that already-at-the-value changes are refused rather than treated as a silent success, which an agent might find surprising given idempotentHint=true; this is not a contradiction of state, but it is worth noting.

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?

Front-loaded with the core action and limit, then the rejection rules and the alternative tool. The parenthetical list of protection-lowering settings is dense and long, but every clause carries decision-relevant information and nothing is padding.

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 batch mutation with a rich enum schema and an existing output schema, the description covers what is needed: pre-validation behavior, refusal categories, the escape hatch sibling, partial-failure reporting, and zone lookup scope. Return-value shapes are left to the output schema, which is correct.

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 100%, and the schema already documents the 1-20 bounds, per-setting cardinality, ordering and per-value domains for every setting. The description mostly restates ordering and the 20-item cap, adding no new parameter-level syntax or format guidance. Baseline 3 is appropriate when the schema carries this much.

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 with scope: 'Change 1 to 20 settings of a Cloudflare zone, in order.' It goes further and names the sibling tool that handles the excluded case ('use cloudflare_zone_setting_weaken for those'), so an agent can separate this tool from cloudflare_zone_setting_weaken without inspecting either schema.

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?

Enumerates the concrete conditions under which nothing is sent (invalid value, already-at-value, plan restriction, protection-lowering change) and routes the last case to a specific alternative tool. It also adds a scope constraint ('Zones are looked up only in the account's own zones'), which tells the agent what lookups will and will not succeed.

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