argo_app_diffIdentify which resources are out of sync in an ArgoCD application, so you can diagnose configuration drift and determine what needs reconciliation.
Show what's out of sync for an ArgoCD application.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Application name |
| Name | Required | Description | Default |
|---|---|---|---|
| diff | Yes | ||
| hasDiff | Yes | ||
| retained | No |
Changes observed during successful MCP inspections.
v5.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already establishes the safe read-only nature. The description reinforces that this is a read operation but adds no behavioral context such as how the diff is computed, whether it contacts the cluster, or permission requirements.
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 a single front-loaded sentence with no wasted words. It efficiently communicates the core action.
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 one-parameter read-only tool with an output schema and annotations, this is largely complete. The main gap is the absence of sibling differentiation, but the core operation is clear.
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 100%, and the single `name` parameter is documented in the schema. The description adds no parameter meaning beyond the schema, so the baseline of 3 is appropriate.
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 states a specific verb and resource: showing what is out of sync for an ArgoCD application. This distinguishes it from a general app detail or health summary, though it does not explicitly name the sibling tools it differs from.
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?
It implies the tool is used for sync drift inspection, but gives no explicit when-to-use guidance, prerequisites, or alternatives. Sibling tools like argo_app_detail and argo_app_health_summary are not mentioned, leaving the agent to infer selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.