Cloudflare: Delete kv key

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is structured data. The description's "value is permanently lost" reinforces this but adds no new trait such as propagation delay, behavior when the key is absent, or whether the namespace must be empty.

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 short sentences with the destructive warning placed prominently after the action statement; little wasted text. The "[UNIFIED]" prefix is extraneous but harmless.

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 destructive, four-parameter mutation with no output schema and zero schema documentation, the description should at minimum disambiguate the site/account_id/namespace_id identifiers and describe the success response. It covers only the permission requirement and the destructive nature, both of which are partly redundant with annotations.

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 four parameters, so the description carries the full burden — and it names none of them. It never clarifies the relationship between site, account_id, namespace_id, and key_name, leaving an agent to guess how account_id interacts with site and namespace scoping.

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 ("Delete a single KV key") and scopes it to one key rather than a namespace, which separates it from cloudflare_delete_kv_namespace. It does not explicitly name or route to any sibling, so it falls short of full differentiation.

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?

It discloses the prerequisite (Workers KV Storage Edit permission), which is genuinely useful context for when the call will succeed. However, there is no statement of when to use this versus cloudflare_delete_kv_namespace or how to confirm a key exists first, so usage is only implied.

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