list_accounts

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

With no annotations present, the description carries the burden of behavioral disclosure. It discloses the read-only nature ('List'), the authorization scope ('accessible with the current API token'), and the return substance ('account details such as ID, name, and settings'). Pagination behavior is not described, but it is largely covered by the input schema.

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 sentences with no filler. The first sentence front-loads the action and scope, and the second sentence defines the return shape. Every clause contributes useful 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?

For a simple read-only list tool with no output schema, the description gives enough context about the resource, credential scope, and return values. Combined with fully documented pagination parameters, it is nearly complete; the only minor gap is that pagination behavior is not explicitly stated in the description.

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?

All three parameters are fully documented in the schema (name filter, page, per_page), so the baseline is 3 even without parameter details in the description. The description adds no new parameter semantics beyond what the schema already provides.

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 states an explicit verb ('List'), a specific resource ('Cloudflare accounts'), and a binding scope ('accessible with the current API token'). This clearly separates it from sibling tools like list_zones and list_dns_records, even without naming alternatives.

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 phrase 'accessible with the current API token' implies the intended context, but the description never explicitly states when to use this tool versus alternatives or when not to use it. No sibling-tool exclusions or fallback guidance are provided.

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