cf_d1_list_databases

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 discloses what the output contains (ids, creation timestamps, wrangler bindings), which is useful, but says nothing about read-only nature, pagination, rate limits, or account-scope/auth requirements for a list operation.

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 efficient sentence, front-loaded with the resource and account scope. Every clause earns its place by naming the resource and the returned fields; no filler.

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 an output schema present, return values needn't be explained, and with zero parameters the schema side is trivial. The description covers scope and payload composition adequately, though it omits any pagination or scope caveats an agent might want.

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 baseline is 4 per the rubric. The description adds nothing that could be misread as a parameter requirement, which is correct for a parameterless listing tool.

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+resource ('List all D1 (serverless SQLite) databases in the account') and even enumerates the returned fields (ids, timestamps, wrangler bindings). It is clearly distinguishable from cf_d1_query and cf_d1_schema, though it doesn't explicitly name those siblings. Strong but not sibling-differentiating.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named despite siblings like cf_d1_query and cf_d1_schema existing. Usage is only loosely implied by the word 'List'. No prerequisites or account/auth context are stated.

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