jp_lit_delete_cache

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

Annotations already indicate destructive (destructiveHint: true) and non-read-only (readOnlyHint: false). Description adds that session history is not deleted but cache body cannot be restored, providing useful context. No contradiction.

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?

Three sentences in Japanese are concise and front-loaded with the action. Slight redundancy in the warning about irreversibility could be tightened.

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 the destructive nature and presence of annotations, the description adds necessary context about irreversibility and session history. An output schema exists but is not shown, so completeness is adequate.

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?

Input schema shows zero parameters, but description mentions 'cache_key' and 'clear_all=true', which are not reflected in the schema. This creates confusion about how to invoke the tool.

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 clearly states the tool deletes local cache by cache_key or clear_all=true, distinguishing it from siblings like jp_lit_list_cache and jp_lit_prune_cache.

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 suggests using jp_lit_list_cache for pre-deletion check and jp_lit_prune_cache with dry_run=true for safe inspection, plus warns that cache body is irreversible.

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