refresh_gitops_application

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

With no annotations, the description must carry the behavioral burden. It is explicit that this is a mutation ('patching') and identifies the exact annotation, which is more than a bare verb. However, it does not disclose consequences of a forced refresh, idempotency, or required permissions.

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?

A single, front-loaded sentence that states the operation and mechanism with no redundant words. It is concise while carrying the most important semantic content.

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 simple patch action, the description covers the core operation and an output schema exists, so return-value documentation is not required here. Still, the absence of any side-effect or alternative-tool context, especially the distinction from sync_gitops_application, leaves the agent with an incomplete picture for safe selection and invocation.

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?

Schema description coverage is 0% and the description does not explain the parameters. It only implies that `name` targets the Application; `cluster` and `namespace` are left to their titles/defaults with no guidance on when to override them. The description fails to compensate 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 names a specific action ('Force-refresh'), the exact resource ('ArgoCD Application'), and the implementation mechanism ('patching the argocd.argoproj.io/refresh annotation'). This is enough to distinguish it from sibling operations like get_gitops_application or sync_gitops_application.

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?

There is no guidance about when to choose refresh over the related sync_gitops_application, nor any exclusions or prerequisites. The only usage hint is the verb itself, which does not help an agent choose among the GitOps siblings.

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