list_partner_shadow_zone_hosts

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read operation via 'List', but discloses nothing about pagination, result limits, auth requirements, or what happens with unknown inputs. The bare scope sentence leaves significant gaps for a no-annotation tool.

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 well-formed sentence with the resource front-loaded and no wasted words. Slightly terse given its total lack of behavioral context, but structurally clean.

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?

There is no output schema and no annotations, yet the tool is a simple filtered list with fully documented parameters. The definition says enough to invoke it correctly, but a reader gets no sense of what a 'partner-discovered shadow zone' is or what the response contains.

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 100%, and each parameter already has a descriptive schema entry, so the baseline is 3. The description's phrase 'for a Cloudflare account, partner, and domain' merely restates the three required parameters without adding format or constraint detail.

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?

Specific verb 'List' plus resource 'hosts in a partner-discovered shadow zone', scoped to account/partner/domain. It is clearly distinguishable from list_partner_shadow_zones (which lists zones, not hosts), though it does not explicitly contrast with the very similar list_zone_partner_shadow_hosts sibling.

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 states what can be listed but gives no when-to-use guidance, no prerequisites, and never names an alternative such as list_partner_shadow_zones or list_zone_partner_shadow_hosts. The agent must infer usage entirely from the name.

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