Clear Cache

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

With no annotations, the description carries the full behavioral burden. It does disclose one real trait — the next request re-downloads, implying a performance cost — but says nothing about permissions, whether the clear is scoped/reversible, or impact on in-flight requests.

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?

Two short sentences, zero padding, with the core effect front-loaded before the enum clarification. Every sentence earns its place.

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 single-parameter, no-output-schema tool this is nearly sufficient, but with no annotations the description should at least flag that clearing forces a costly re-download and how this differs from alg-refresh-cache and alg-cache-stats. The enum nuance is covered; the operational context is not.

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 coverage is 100%, so baseline is 3, but the description genuinely adds meaning the schema lacks by defining what the 'docs' enum value encompasses (documentation, scenarios, workshops), which is not derivable from the schema's generic 'Cache source to clear'.

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?

'Clear cached GitHub data so the next request re-downloads it' is a specific verb+resource with the consequence spelled out. It doesn't however distinguish itself from the sibling alg-refresh-cache, leaving the clearing-vs-refreshing boundary unstated.

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 on when to clear versus when to use alg-refresh-cache, and no warning about side effects (forced re-download cost, latency). The agent must infer the scenario entirely from the tool name.

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