Clear Cache

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

No annotations are supplied, so the description carries the full burden; it does disclose what is cleared (OpenCart and Journal3 caches) and the access requirement (SSH or DDEV), which is exactly the kind of auth/environment context the rubric credits. It stops short of stating side effects such as downtime, whether clearing is reversible, or whether the site must be reloaded afterward.

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, eleven words, with the action and scope front-loaded and the prerequisite following. Nothing is padded or repeated from the name/title.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, cache scope, and the access prerequisite. For an unannotated, potentially disruptive cache-clear operation, a note about operational impact would make it fully 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?

The tool takes zero parameters, so the schema imposes nothing to document and the baseline for this dimension is 4. No additional parameter meaning is needed or missing.

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 named resources ('OpenCart and Journal3 caches') plus the environment ('on VPS'), so an agent immediately knows what the tool does. It does not explicitly distinguish itself from the closest sibling, refresh_modifications, but the overlap risk is low.

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 'Requires SSH or DDEV' clause is a genuine execution prerequisite that tells the agent the conditions under which this tool can even run. However, it gives no when-to-use guidance relative to alternatives such as refresh_modifications, nor any when-not-to-use exclusions.

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