Cloudflare: List kv namespaces

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine context beyond that: the required permission scope, the need for an account ID, and the returned fields (id and title), which is more than the annotation alone conveys.

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 tight sentences with the resource and scope front-loaded, followed by preconditions and return shape. The "[UNIFIED]" prefix is minor noise but does not obscure the content.

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?

Return values are described, so the lack of an output schema is not a gap. But with three parameters at 0% schema coverage, an agent cannot determine how to use site or per_page from this definition, leaving it adequate but incomplete.

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%, so the description must carry parameter meaning, but it only hints at account_id ("Account ID"). The per_page pagination parameter and the required site parameter are entirely unexplained in both schema and description.

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?

States a specific verb and resource ("List Workers KV namespaces in the account") with a clear scope (account-level). It is distinguishable from siblings like cloudflare_list_kv_keys or cloudflare_create_kv_namespace by resource and read-only nature, though it never names an alternative explicitly.

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?

Adds useful preconditions (Workers KV Storage permission and Account ID), which tells an agent what it needs before calling. However, there is no when-to-use/when-not guidance and no routing to related tools such as cloudflare_list_kv_keys for keys within a namespace.

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