get_gitops_application

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

With no annotations, the description carries the full burden. It indicates a read operation ('Get... details') and lists returned fields, which is adequate but does not disclose limitations, permissions, or whether it requires specific cluster access. It is acceptable but not thorough.

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 that conveys the essential purpose and output without unnecessary words. Every part adds value.

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?

Given the tool has an output schema (not shown) and only one required parameter, the description covers the key returned fields adequately. However, it does not mention any limits, ordering, or error conditions, but for a read tool with a clear scope, it is mostly complete.

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 0%, meaning the description must compensate for parameter meaning. However, the description does not explain the role or constraints of 'name', 'cluster', or 'namespace' beyond their existence in the schema. The default values are present in the schema but not elaborated in the description.

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 clearly states the tool's purpose: to get ArgoCD Application details, listing specific data points (sync, health, repo, path, destination, resources table). It uses a specific verb ('get') and resource ('ArgoCD Application'), distinguishing it from sibling tools like 'sync_gitops_application' or 'get_resource'.

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?

No guidance is provided on when to use this tool versus alternatives. The sibling set includes 'sync_gitops_application' and many other get/list tools, but the description does not specify context, prerequisites, or when not to use this tool.

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