clear_cache

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds context that it clears caches and is useful for stale data, reinforcing that it's a non-destructive mutation. It doesn't introduce new side effects beyond what annotations imply, but the added usage scenario improves 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 concise, consisting of two sentences that directly state the action, scope, and use case. No redundant or irrelevant information is present, and it is well-structured for quick comprehension.

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 schema and annotations, the description provides sufficient context: it explains what the tool does, when to use it, and the parameter is fully documented. The presence of an output schema means return values are not required in the description, and the existing details cover all necessary information.

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 includes a single parameter 'scope' with a detailed description explaining each allowed value ('galaxy', 'docs', or null to clear all). The description also mentions the scope types, though less precisely. Together, they provide complete semantic understanding of the parameter.

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: it clears server caches, specifically listing the types of caches (Galaxy version/docs-blob, standalone-role v1, doc manifest/page, or both). This distinguishes it from sibling tools which are primarily search/get operations, making the purpose unambiguous.

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 provides a specific use case: 'Useful when cached data becomes stale during long-running sessions.' This gives clear guidance on when to invoke the tool. It doesn't explicitly contrast with alternatives, but no direct alternative exists, so the guidance is adequate.

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