kv_delete

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

Adds critical behavioral context about the human-approval gate and preview return beyond the annotations' destructiveHint. Annotations already indicate destructive nature, but description elaborates on the execution safeguard.

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 sentences, no extraneous information. Every word serves a purpose.

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?

Lacks details about the response format of the preview, behavior for non-existent keys, and the optional account_id fallback. IdempotentHint is noted but not explained. Adequate for simple use, but gaps exist.

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 covers all 4 parameters with descriptions, so additional semantics are minimal. The description reinforces the confirm gate but adds no new parameter-level details beyond the schema.

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?

Clearly states 'Delete a key from a KV namespace' with specific verb and resource. Distinguishes from sibling kv_get, kv_put, and other delete tools.

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?

Explicitly mentions the confirm:true requirement and preview behavior, guiding when to execute vs preview. Does not compare to alternative tools like kv_put or other deletion methods.

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