Argocd Invalidate Cluster Cache

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

Annotations already declare idempotent=true and destructiveHint=false, so the safety profile is partly covered. The description meaningfully reinforces this by clarifying that the operation "removes nothing real" — important reassurance given readOnlyHint=false, which could otherwise make an agent hesitate. It does not state whether a resync/refresh cost or timing is involved.

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 short sentences with zero padding: the action and its non-destructive nature are front-loaded, and 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?

An output schema exists and annotations cover the safety profile, so the description is not obliged to explain return values. Purpose, trigger, and non-destructiveness are all present; only the mechanics of what happens after invalidation (cache rebuild behavior) are left implicit.

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?

With one parameter at 100% schema description coverage, the schema fully documents that it accepts a cluster name or server URL. The description adds no parameter-level meaning beyond that, so the baseline of 3 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?

The description names a specific verb (invalidate) and resource (a cluster's cached resources) and explains the user-visible symptom it addresses (phantom OutOfSync or Unknown health). No sibling tool overlaps with this function, so explicit differentiation isn't needed, but it also doesn't route against alternatives.

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 standard fix for phantom OutOfSync or Unknown health" gives a clear, concrete trigger for when to reach for this tool. It stops short of stating when not to use it or naming an alternative diagnostic (e.g. get_resource_tree) first, so it is clear context without exclusions.

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