cache_delete

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

Declares destructive and irreversible nature, safe handling of non-existent keys, and return value (count of deleted keys). No annotations provided, but description fully covers behavioral traits.

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?

Concise, front-loaded with delete action, then explains implications and usage. Every sentence is informative without excess.

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?

No output schema needed since return value is described. Description covers all necessary context for using this tool correctly.

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?

Adds context beyond schema: instance_id should come from list_instances, keys must be exact (no glob) and recommends cache_keys to list. Schema coverage is 100% so baseline is 3, but description adds significant value.

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 it permanently deletes keys from a running cache instance, distinguishing it from siblings like cache_set, cache_keys, and delete_instance.

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 states when to use (remove stale entries), when not to use (prefer cache_set with short TTL, don't clear entire instance), and names alternatives (cache_set, delete_instance, dashboard).

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