ArgoCD applications

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

readOnlyHint=true already tells the agent this is a safe read. The description adds that results come back as a structured summary rather than a table, which is useful shaping context, but it says nothing about pagination, cluster/context requirements, or what happens if no project is given.

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 the purpose front-loaded and no filler. The second sentence is marginally redundant given the output schema but still contributes signal about result shape.

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, so return values need no explanation, and annotations cover safety. The remaining gaps are the unmentioned filter capabilities and the lack of routing guidance among three closely related argo_* siblings, which an agent would need to choose correctly.

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 coverage is 100%, so both 'project' and 'selector' are already documented in the schema. The description never mentions that filtering by project or label selector is possible, so it adds nothing beyond the schema and cannot lift the baseline.

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?

States a specific verb and resource ('List ArgoCD applications') plus the content scope ('sync/health status'), so an agent knows exactly what it returns. It does not explicitly differentiate itself from siblings like argo_app_health_summary or argo_app_detail, which keeps it short of a 5.

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 statement of when to use this versus argo_app_detail, argo_app_diff, or argo_app_health_summary, which cover overlapping territory. The only contrast offered ('structured summary instead of table output') describes output format, not tool selection.

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