clear_reader_cache

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

The description correctly identifies the destructive nature (clearing cache) consistent with destructiveHint annotation. It adds value by explaining the scope options (URL, domain, all). No contradictions.

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?

Single sentence of 10 words, front-loaded with the verb, no unnecessary words. Perfectly concise.

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 cache-clear tool with two optional parameters and an existing output schema, the description provides complete context. It specifies all clearing modes and relies on the output schema for returns.

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?

With zero schema description coverage, the description fully explains both parameters and their interaction: clearing by exact URL, domain, or all entries if both omitted. This is critical for correct usage.

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 action (clear) and resource (pyaireader cache entries) with specific modes (by URL, domain, or all). It effectively differentiates from sibling tools like read_url or storage_status.

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 explicit guidance on when to use this tool versus alternatives, nor any when-not conditions. The description implies usage for cache clearing but lacks context about prerequisites or side effects.

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