get_gitops_application_health

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

With no annotations, the description carries the burden and does convey that this is a read-only health lookup returning per-resource status. However, it does not disclose anything about authorization, what happens when the application is missing, or whether health data is cached/stale.

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 sentence with no wasted words; the key information is front-loaded. It is concise without being tautological.

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 tool with 3 parameters, no annotations, and 0% schema coverage, one sentence is not enough. It omits parameter semantics and fails to guide selection among the many GitOps-related siblings, despite the output schema covering return values.

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 three parameters. The defaults hint at namespace, but the meaning of cluster and how name refers to the ArgoCD Application are left to inference.

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 precise verb ('Get'), a specific resource ('per-resource health status'), and a target ('ArgoCD Application'). This clearly differentiates from siblings like get_gitops_application or refresh_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?

The purpose implies when to use it—when per-resource health of an ArgoCD Application is needed—but it does not explicitly contrast with sibling tools such as get_gitops_application or refresh_gitops_application, nor state when not to use it.

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