clear_cache

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

Annotations declare readOnlyHint=false, correctly indicating this is a mutating operation. The description adds the effect ('force fresh data on next query') and the scope (source-specific or all). However, it does not disclose potential consequences such as performance impact or irreversibility of clearing all cached data. Since annotations already signal the mutation, the bar is lower and the description meets it adequately.

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 concise sentences front-load the action and purpose. Every word earns its place, and there is no redundancy or filler. The structure is ideal 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?

For this simple utility tool with one optional parameter, no output schema, and only a readOnlyHint annotation, the description covers the core aspects: what, when, and how. It could be improved by mentioning what the tool returns or any warning about clearing all, but the description is largely complete for its simplicity.

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 has one parameter 'source' with a 100% descriptive coverage, including a detailed list of valid values and 'Omit for all.' The tool description reiterates this ('Specify a source name or omit to clear all') but does not add significant semantic meaning beyond the schema. Baseline 3 is appropriate given the high schema coverage.

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?

Description clearly states what the tool does: 'Clear cached API responses to force fresh data on next query.' The verb 'clear' and resource 'cached API responses' are specific, and the purpose is explicit. It is distinct from sibling tools, none of which deal with cache management.

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 context for when to use the tool ('to force fresh data on next query') and explains the sole parameter's behavior ('Specify a source name or omit to clear all'). It does not explicitly state when not to use it or mention alternatives, but given there are no alternative cache-clear tools, this is sufficient.

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