Cloudflare: List accounts

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

readOnlyHint=true already tells the agent this is a safe read. The description usefully adds that results are scoped to the stored token rather than all accounts, which is real behavioral context. It says nothing about pagination, empty results, or what happens when the token is invalid or lacks account scope.

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?

Two tight sentences, purpose first, rationale second, with no filler. The "[UNIFIED]" prefix is the only piece of noise that does not earn its place.

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 one-parameter read-only listing tool with no output schema, the description covers purpose, scope, and return fields well. The one meaningful hole is the undocumented required `site` argument, which is a required input the agent must supply blind.

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 single required parameter `site` has 0% schema description coverage and the description never mentions it, so the agent gets no meaning for it from either source. With coverage this low the description should explain what `site` selects, especially since the tool is otherwise account-scoped rather than site-scoped.

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?

The description gives a specific verb and resource ("List Cloudflare accounts") plus the scope (accounts visible to the stored API token) and the return shape (id + name). The second sentence distinguishes it from the resource-specific list tools by naming its role as an Account ID discovery step for Workers/KV/R2.

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?

It states a clear trigger condition: use this when the site does not pin an Account ID and you need one for Workers/KV/R2 tools. It does not spell out the inverse (when an Account ID is already known, skip this), but the conditional framing gets the agent most of the way there.

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