refresh_cache

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

Annotations already indicate destructive behavior (destructiveHint: true). The description adds valuable context that omitting resource_id refreshes all cached resources, clarifying the tool's scope. However, it does not disclose potential side effects (e.g., blocking, permissions) beyond the annotation.

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 extremely concise: two sentences with no redundant information. The main action is front-loaded, and the argument description is directly below. Every sentence serves a purpose.

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 tool with one optional parameter and an output schema, the description covers purpose and parameter behavior. It lacks details on error scenarios or sync/async behavior, but given the output schema and annotations, it is adequately complete.

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 0% schema description coverage, the description fully compensates by explaining the single parameter: 'resource_id: Specific resource to refresh (prefixed or bare ID), or omit to refresh all.' This adds format notes and default behavior, making the parameter self-documenting.

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 tool's function: 'Re-download cached resources to get the latest data.' This uses a specific action verb ('re-download') and resource ('cached resources'), effectively differentiating from siblings like cache_info (info) or check_freshness (check).

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 implies usage when needing latest data from cache but provides no explicit comparisons to sibling tools like download_resource or cache_manage. Without guidance on when to prefer this tool over alternatives, the description offers only implied context.

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