Clear the entire fetch cache.
Use when you need fresh data and don't want to rely on cached results.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It states the core behavior 'Clear the entire fetch cache,' which implies a destructive action, but does not disclose side effects like irreversibility, impact on other users, or permissions needed. The behavior is not hidden, but context is minimal.
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, each earning its place: the first states the action, the second gives the trigger for use. No fluff, front-loaded, and appropriately sized for a simple 0-parameter tool.
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 (0 params), the presence of an output schema (so return values need not be described), and the clear usage guidance, the description is largely complete. A minor gap is the lack of an explicit warning about the global/destructive nature, but 'entire' conveys the scope.
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 tool has zero parameters, and the description does not need to explain any. The schema coverage is 100% (vacuously true), and the description appropriately avoids inventing parameters. Baseline for zero-param tools is 4, and no extra credit is needed.
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 specific action 'Clear the entire fetch cache' with a verb and resource, distinguishing it from sibling tools like cache_stats (inspect), fetch_markdown, or fetch_url (retrieve). It leaves no ambiguity about what the tool does.
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 gives a direct use case: 'Use when you need fresh data and don't want to rely on cached results.' This provides clear context, though it does not explicitly name alternatives or exclusion scenarios (e.g., when cache_stats would be more appropriate).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
fetch_url and fetch_markdown both fetch URLs, but fetch_url returns raw HTML+markdown while fetch_markdown returns only markdown, which is a clear distinction. check_domain, cache_stats, and clear_cache are all distinct. The overlap is minor and well-handled by descriptions.
Most tools use a verb_noun pattern: check_domain, clear_cache, fetch_markdown, fetch_url. cache_stats deviates slightly, being a noun_noun phrase, but it's still clear and consistent enough.
With 5 tools, the set is well-scoped for a fetch/cache utility. Each tool serves a distinct purpose without redundancy or bloat.
The tool surface covers the core lifecycle: fetching with two output formats, cache inspection, cache clearing, and domain health checks. No obvious gaps for the stated purpose of reliable fetching with caching and circuit breaking.