Get Cloudflare Zone Settings

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds genuinely new behavior: it warns when SSL mode is `off` or `flexible` (origin fetched over plain HTTP) and documents the CLOUDFLARE_REAUTHORIZE_REQUIRED error with a concrete one-click reconnect remedy.

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?

Three sentences, front-loaded with the resource and the settings list, then the warning and the error remediation. Dense but every sentence carries distinct information; minor length from the enumerated settings list.

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 no output schema, the description carries the return-value burden and does so by naming the settings returned, the warning condition, and the error code with recovery steps. An agent has what it needs to call and interpret the result.

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?

Only one parameter (domain) with 100% schema description coverage, so the schema already fully documents it. The description adds no format or syntax detail beyond the schema, making the baseline 3 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?

States a specific verb (read) and resource (Cloudflare zone settings) and enumerates the exact settings returned (ssl mode, always_use_https, min_tls_version, etc.), which distinguishes it from siblings like get_cloudflare_zone and set_cloudflare_zone_settings.

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?

Anchors usage to a clear context ('settings that matter after a move') and gives explicit remediation for the CLOUDFLARE_REAUTHORIZE_REQUIRED case. It does not, however, contrast this with get_cloudflare_zone or get_cloudflare_connection, so the alternative-selection guidance is incomplete.

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