Clear Cache

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

No annotations are provided, so the description must fully disclose behavior. It only says 'Clear' but doesn't explain effects like irreversibility, impact on users, permission requirements, or what is destroyed. This is a significant gap for a potentially destructive action.

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 short sentence, concise and to the point. No unnecessary words, but could be more informative. It is appropriately front-loaded.

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 simple structure (1 optional param, no output schema, 100% schema coverage), the description is adequate but minimal. It does not explain behavior for different enum values or return values. Sibling tools related to cache add context, but description could be more complete.

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 description coverage is 100% (only parameter described). The description adds 'Cache source to clear' which is consistent with the schema. Since coverage is high, baseline is 3; the description does not add substantial new meaning 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?

The description 'Clear cached knowledge sources or entire cache' clearly states the action (clear) and the resource (cached knowledge sources), with the ability to target specific sources or all. The enum options in the schema further specify the exact sources. This distinguishes it from sibling tools like alg-cache-stats (statistics) and alg-refresh-cache (refresh).

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. There is no mention of prerequisites, when clearing cache is appropriate, or what to consider before clearing. The description lacks context for decision-making.

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