clear_translation_memory

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

The description discloses destructive behavior, which is critical for a mutation tool. However, without annotations, it lacks details on side effects, revertibility, or return values. The warning is helpful but minimal.

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 extremely concise with only two short sentences, both essential. It front-loads the action and adds a critical warning, with no superfluous text.

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 simple destructive action with no parameters or output schema, the description covers the essential purpose and usage caveat. It could mention confirmation process or return behavior, but the tool's minimal complexity makes this sufficient.

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 tool has no parameters, so the description need not explain any. The mention of 'entire cache' implicitly clarifies scope. Baseline for zero parameters is 4, and the description meets expectations.

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 it wipes the entire translation-memory cache, specifying the resource and action. The verb 'wipe' and 'entire cache' leave no ambiguity about what the tool does, and it contrasts with other translation memory operations.

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?

The description explicitly warns that the tool is destructive and requires user confirmation, providing clear guidance on when to call. However, it does not suggest alternative tools for non-destructive operations, which are available among siblings.

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