kv_keys_list

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

No annotations are provided, so the description must convey behavior. It discloses prefix filtering and pagination capabilities, which are also in the schema. However, it does not mention read-only nature, permissions, rate limits, or return format. The read-only nature is implied but not explicitly stated.

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?

The description is a single sentence of 14 words, front-loaded with the verb 'List'. Every word contributes value with no redundancy.

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?

This is a simple list tool with high schema coverage and no output schema. The description covers the core operation but does not explicitly state that the response includes a pagination cursor. Given the low complexity and schema richness, it is mostly complete.

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 4 parameters are fully described in the schema (100% coverage). The description adds no additional parameter semantics beyond mentioning prefix filtering and pagination, which are already captured by the schema descriptions.

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 and resource: 'List keys in a Cloudflare KV namespace'. This clearly distinguishes it from sibling tools like kv_key_get and kv_key_put. Mentioning 'optional prefix filtering and pagination' further scopes the operation.

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 usage (you use it to list keys), but provides no explicit when-to-use or when-not-to-use guidance. It does not name alternatives like kv_keys_count or kv_keys_bulk_get, leaving the selection decision to the agent's inference.

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