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

With no annotations, the description carries the full burden of disclosing behavior. It states the destructive action (deleting all keys with a prefix) but omits critical details: irreversibility, permission requirements, whether the operation is atomic, or any side effects on related data. This is insufficient for a bulk deletion operation.

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, front-loaded sentence with no filler. It efficiently conveys the core action and target. There is no redundancy or unnecessary detail, which is appropriate for a straightforward tool.

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?

Given three parameters, no output schema, and no annotations, the description is far too sparse. It does not explain return values, error conditions, the meaning of slug, or the behavior when the prefix matches no keys. An agent cannot reliably invoke this tool correctly with the provided information.

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?

The schema only documents owner_key (33% coverage); slug and prefix have no descriptions. The description mentions 'prefix' implicitly but does not explain what slug represents, the relationship between slug and prefix, or how owner_key affects the operation. The description fails to compensate for the undocumented parameters.

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 'Delete all KV keys starting with a prefix' is specific: it names the action (delete), the target (all KV keys with a given prefix), and clearly distinguishes itself from sibling kv_delete which targets a single key. This is unambiguous and directly states the resource scope.

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?

No guidance is provided on when to use this tool versus alternatives like kv_delete or kv_cas. There is no mention of conditions, prerequisites, or cases where a different tool would be more appropriate. The agent is left to infer usage context.

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