clear_cache

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

Describes behavioral effect (evicts caches) and context (stale data). Annotations declare destructiveHint=false, and description aligns, adding detail about what is destroyed (in-memory caches but not index). 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?

Two sentences: first states action and scope, second gives usage guidance and sibling differentiation. Concise and front-loaded with no wasted words.

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 zero parameters, no output schema, and clear annotations, the description is fully complete. It covers purpose, usage, and what it does not do, which is sufficient for agent decision.

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?

No parameters in schema (0 params), so baseline is 4. Description does not need to add param info; it correctly implies no input required.

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?

Clearly states the action (evict all in-memory caches) and specifies the cache types (folder list, message metadata, analytics data). Distinguishes from sibling tool 'clear_index' by noting it does not affect the persistent SQLite index.

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 tells when to use: when cached data appears stale after external mailbox changes (e.g., via Proton webmail). Provides explicit exclusion: 'Does NOT affect the persistent SQLite index — use clear_index for that.'

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