List Cloudflare Inventory

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds genuinely useful non-obvious behavior: it works even when the Cloudflare account isn't connected, letting the agent plan during authorization. It does not discuss pagination or ordering for a full-account listing.

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, well front-loaded with the resource and the state vocabulary before the workflow guidance. Slightly dense with the parenthetical reason examples, but every sentence carries information.

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 takes on the burden of describing the return shape, and does so by specifying the `state` enum and the accompanying human-readable reason. For a zero-param read tool this leaves nothing an agent needs missing.

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?

The tool takes zero parameters, so the schema-baseline is 4. There are no arguments whose semantics need explaining, though the description usefully characterizes the returned `state` field values.

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 ('List every domain in the account') and immediately scopes the output to Cloudflare eligibility. The enumeration of state values (eligible/warn/blocked/connected/inprogress) makes clear this is not the plain list_domains sibling but a Cloudflare-readiness view.

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?

Explicitly says to 'read this BEFORE queueing so you can tell the user what will move and what won't,' establishing a clear ordering relative to the queue step. It does not name the specific sibling (get_cloudflare_queue / connect_domains_to_cloudflare) it precedes, so it stops short of 5.

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