Svuota la cache

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior. The description goes beyond them by specifying what exactly is purged (in-memory and, if enabled, on-disk cache) and by reassuring the caller that no remote Fatture in Cloud state is affected. It omits that later calls may be slower while the cache repopulates, so it is good but not exhaustive.

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?

Short and front-loaded: the action comes first, then the when-to-use, then the scope caveat. The trailing English sentence is a redundant restatement of the Italian opener and slightly dilutes conciseness.

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?

With no parameters, rich annotations, and no output schema needed, the description covers the essentials: what is cleared, why you would clear it, and what is untouched. Only the expected return shape and the transient post-clear slowdown are unstated.

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 description carries no parameter burden and the schema is trivially complete (100% coverage, empty properties object). Baseline for a no-parameter tool applies.

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 and resource ('svuota la cache locale del server') and immediately scopes it as in-memory plus on-disk, which no sibling tool does. It is trivially distinguishable from the read-only Fatture in Cloud data tools and explicitly notes it does not touch remote data.

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?

Gives a concrete triggering condition: use it when a value changed in the web app is not showing as updated. It also states a negative scope ('Non tocca nulla in Fatture in Cloud'), though it names no alternative tool or ordering constraint.

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