cache_clear

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

No annotations exist, so the description must convey behavioral traits. It clarifies that the action is to clear keywords and that page ranges are optional, but it doesn't mention side effects like whether the operation is reversible or affects only the keyword cache. 'Clear' implies deletion, but further details on impact or return value would improve transparency.

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 two sentences and a usage note, with no filler. Each sentence adds distinct value: purpose, parameter behavior, and use case. It is front-loaded with the core action and remains succinct.

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 tool's simplicity (one optional parameter, no output schema, no annotations), the description covers purpose, usage, and parameter semantics well. It lacks explicit return value information, but for a cache-clear operation this is not critical. It adequately distinguishes from sibling cache tools and provides sufficient context for most use cases.

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 input schema provides only the parameter name 'pages' with a type and default, but no description. The description compensates by explaining the format ('1-500') and the conditional behavior (clears only those pages when specified). It does not explicitly state what happens when pages is empty, but the conditional phrasing implies clearing all, which is a minor gap.

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 'Clear cached keywords' with a specific verb and resource, distinguishing it from sibling tools like cache_status and cache_query. It also adds nuance by explaining the optional page range behavior.

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 includes an explicit 'USE THIS TOOL WHEN' section stating to use it when refreshing stale cache or freeing space. It doesn't mention when not to use it or alternative tools, but the context is clear enough for straightforward selection.

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