Refresh Modifications

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

With no annotations, the description carries the burden and does well: it discloses the exact mutation effect (cache cleared, unmodified files served) and a hard limitation (no full recompile). It does not state permissions or whether the action is safe/idempotent, but it covers the most important behavioral trait for a cache-clearing tool.

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, no waste; the primary effect is front-loaded and the caveat immediately follows. Every clause earns its place.

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?

Complete for a no-argument, no-annotation mutation: it explains what is cleared, what the user must do next, and what the tool cannot do. Output schema exists, so no return-value explanation is needed.

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?

Zero parameters, so baseline is 4. The description adds no parameter info because there are none to describe.

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?

States a specific verb (Clear) and resource (OCMOD modification cache) with a clear effect (serves unmodified files). Distinguishes itself from sibling 'clear_cache' and 'get_modifications' by naming exactly which cache and what it does not do.

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?

Explicitly states the follow-up step needed (Admin > Extensions > Modifications > Refresh) and that this tool cannot do it, preventing misuse. This is when-to-use and what-not-to-expect guidance in two sentences.

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