list_accounts

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

With no annotations, the description carries the full burden of behavioral disclosure. It correctly signals a read-oriented list operation and adds the valuable scoping detail that results are limited to what the current API token can access. It does not mention response shape, pagination, or error behavior, but for a parameterless list operation this is a minor gap.

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 that states the verb, resource, and scope without unnecessary words. It is immediately readable and front-loads the core purpose.

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 zero-parameter list tool, the description is largely complete: it tells the agent what it will get and under what access scope. The only missing piece is the return format, which is not documented by an output schema, but this is unlikely to prevent correct selection or invocation.

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?

There are zero parameters, so the schema already covers everything. The description adds no parameter-specific detail because none is needed; the scoping context it provides ('accessible with the current API token') is the only relevant semantic information.

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 uses a specific verb ('List') and clearly identifies the resource ('Cloudflare accounts') along with the exact scope ('accessible with the current API token'). This makes it easy to distinguish from sibling tools like get_account or list_account_members, which operate on different resources or granularity.

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 implies when to use this tool: when you need to enumerate Cloudflare accounts available to the current token. However, it does not explicitly mention alternatives or state when not to use it, leaving the agent to infer the routing decision from sibling names.

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