Clear API Cache

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

No annotations are provided, so the description carries the full burden. It states the primary effect (clearing cache) and implies that after clearing, subsequent operations will see fresh data. However, it does not disclose any potential side effects such as global scope, temporary performance impact, or whether it affects other users. For a simple cache clear, this is acceptable but could be more transparent.

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 short sentences that are front-loaded: it states the action first, then the usage guidance. There is no redundancy or wasted words. Every part contributes meaning.

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 zero-parameter tool with no output schema, the description covers the essential points: what it does and when to use it. It is complete enough for an agent to select and invoke correctly. A slight gap is the lack of clarification on whether this clears only the current user's cache or a shared cache, but overall it is adequate.

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 schema coverage is trivially 100%. The description does not need to explain parameter semantics. Per the rubric, 0 params baseline is 4, and the description adds the necessary context about the operation's purpose.

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 action (Clear) and the specific resource (internal response cache). It distinguishes itself from sibling tools like hosting_cache_clear and agency_cache_clear by focusing on the API-level cache. The phrase "Use when you need fresh data" reinforces the purpose.

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 explicitly says when to use the tool: "Use when you need fresh data after making changes." This provides clear context, but it does not mention any alternative tools or explicitly state when not to use it. Still, the guidance is specific and actionable.

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