code_quality_clear_cache

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

With no annotations, the description discloses the behavior: it clears caches for two backends and allows scoping via project_root. This adds transparency beyond the name, though it does not mention potential side effects or safety implications.

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 consists of two sentences with no redundancy. The first sentence states the main action, and the second provides detail on the parameter. Every word adds value.

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 tool's simplicity (one optional parameter, output schema exists), the description is nearly complete. It could mention if the operation is safe to call repeatedly, but this is non-critical.

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 parameter 'project_root' has no schema description (0% coverage), but the description explains its effect: it limits clearing to one Sonar project's port mapping. This fully compensates for the schema gap.

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 clears in-memory caches for specific backends (Sonar port discovery, JetBrains session). This distinguishes it from sibling tools which focus on inspection and analysis, not 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 implies the tool is used for cache clearing but does not explicitly state when to use it versus alternatives, nor does it provide conditions for not using it. The sibling tools are different in function, but no guidance is given.

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