list_partner_shadow_zones

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List' implies a read-only operation, but nothing is said about pagination, result volume, permissions, or partner/account side effects. For a tool with zero annotation coverage this is thin.

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?

A single front-loaded sentence with no filler; the parenthetical definition is a compact clarification. Nothing is wasted, though there is little structure beyond the one sentence.

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 simple two-parameter list tool with full schema coverage and no output schema, the core is adequate. However, ambiguity against the shadow-host sibling tools is not resolved, and no return-shape or scope hints are given, leaving the agent to infer whether zones or hosts come back.

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%, so both account_id and partner are documented in the schema itself. The description only restates that account and partner scope the result, adding no syntax or format detail beyond the schema. Baseline 3 applies.

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 (List) and resource (partner-discovered shadow zones), and even glosses the term as 'unmanaged domains'. It scopes to a Cloudflare account and partner, but does not distinguish this from the very similar sibling tools list_partner_shadow_zone_hosts and list_zone_partner_shadow_hosts, so an agent can't tell 'zones' vs 'hosts' apart from the description alone.

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 gives no when-to-use guidance, no prerequisites, and no named alternative. Given the cluster of near-identical sibling tools (shadow zone hosts, zone partner shadow hosts, partner insight counts), routing information would be especially valuable here and is absent.

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