ReSharper Reset Cache

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

Annotations already mark the tool destructive, and the description adds what exactly gets destroyed (the ReSharper analysis cache) and the behavioral consequence: the next inspect or cleanup call will rebuild from cold. It also explains the stale-index failure mode, giving the agent a clear mental model beyond the annotation flags.

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 three sentences with no wasted words: it states the action, explains the diagnostic trigger, and flags the cost. The most important operational fact (delete cache) is front-loaded, and the maintenance warning is placed last where it can temper misuse.

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 one-parameter destructive tool with no output schema, the description is complete. It tells the agent what is deleted, why an agent might want to call it, what the next invocation will experience, and why it should not be used routinely. Annotations already carry the safety profile, so nothing critical is missing.

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 schema already fully documents solutionPath, including override behavior and discovery fallback, so the description does not need to add parameter details. The description mentions solution-level scope generically but adds no parameter-specific semantics beyond what the schema provides, matching the baseline for 100% schema description 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?

The description opens with a specific action and resource: 'Delete this solution's ReSharper analysis cache'. It clearly distinguishes this cache-reset tool from the sibling inspection and cleanup tools by naming the cache as the target and framing the tool as a remedy for stale index issues.

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 gives clear context for when to use the tool: when inspect reports compilation errors that the compiler itself does not, due to a stale index. It also warns 'not routine maintenance' and explains the cold-analysis cost. It references the sibling operations indirectly but does not explicitly contrast with when to choose cleanup or inspect instead.

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