get_argocd_app_status

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses what the operation returns: health, sync status, last sync result, error conditions, and unhealthy/out-of-sync managed resources. The read-only nature is implied by 'Get', and the description avoids hiding side effects. It could add permission or error behavior details, but for a status read this is solid.

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 two sentences with no filler. The first sentence front-loads the tool's purpose and outputs, and the second provides valuable workflow context. Every word 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?

For a single-parameter status read tool with an output schema, the description covers the essential behavior and even suggests the next steps. It is complete enough for correct invocation, though it could mention how to obtain the app name (e.g., from list_argocd_apps) or note behavior when the app does not exist. Minor gap only.

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 explicitly define the 'app' parameter beyond referring to 'an ArgoCD application.' The parameter name and type are self-explanatory enough for a single required argument, and the description implies 'app' is the ArgoCD application identifier, but it does not fully compensate for the lack of schema documentation. This is adequate but not rich.

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 uses a specific verb ('Get') and identifies the exact resource (an ArgoCD application's status), then enumerates the specific status categories covered: health, sync status, last sync operation result, error conditions, and unhealthy/out-of-sync resources. This clearly distinguishes it from the sibling tools like get_live_diff and list_pods.

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 explicitly positions this tool as a 'good starting point before drilling into get_live_diff or the underlying pods,' which gives the agent useful workflow context. It does not explicitly state when not to use it, but the recommended sequencing relative to alternatives is clear.

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