Cloudflare: List kv keys

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

The annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds genuinely new behavioral context: it states the return payload (key names plus metadata) and that results are cursor-paginated, which matters since no output schema exists. It does not cover rate limits, ordering, or behavior when the namespace is empty, so it is a modest rather than rich addition.

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 compact clauses, front-loaded with the action and followed by the permission and return-shape facts; nothing is padded. The leading "[UNIFIED]" tag is metadata noise rather than content, which keeps it from a 5.

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 read-only list tool with no output schema, describing the return shape and cursor pagination is appropriately helpful, and the annotation covers safety. However, with five undocumented parameters and no guidance on how limit/cursor interact, an agent still has to guess how to paginate correctly.

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?

Schema description coverage is 0% across five parameters, so the description carries the full burden and largely fails it: limit, cursor, site, and account_id are never explained, and cursor is only alluded to as a pagination concept without saying it should be passed back from a prior response. Only namespace_id gains any meaning from the phrase "in a KV namespace."

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 keys in a KV namespace") and scopes it to Workers KV, which is enough to distinguish it from cloudflare_list_kv_namespaces and cloudflare_get_kv_value without opening the schema. It stops short of explicitly naming the sibling boundary (keys vs. namespaces vs. values), so it is clear but not maximally differentiated.

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?

Usage is only implied: an agent can infer this is the enumeration step before fetching a value with cloudflare_get_kv_value, but the description never says when to pick this over cloudflare_list_kv_namespaces or when not to use it. The parenthetical about the required Workers KV Storage Read permission is a useful prerequisite hint but is not a usage rule.

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