call-argocd-api

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

With no annotations provided, the description carries full burden. It states the tool is read-only and mutations are blocked, which is key behavioral info. However, the input schema contradicts this by including mutation HTTP methods (POST, PUT, PATCH, DELETE), creating a significant inconsistency that undermines transparency.

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 short sentences, front-loaded with purpose. It is concise without waste. However, it could be slightly improved by addressing the contradiction with schema or adding a brief example.

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 6 parameters including nested objects and no output schema, the description lacks important context such as example API paths, how to handle pathParams/queryParams, what happens when a mutation is attempted, and prerequisites like authentication. The contradiction further reduces completeness.

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% with descriptions for all 6 parameters. The tool description does not add any parameter information beyond the schema, so it meets the baseline of 3. No additional meaning or usage hints are provided.

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 'Execute a read-only Argo CD REST API call (GET)', which clearly identifies the tool as a generic read-only API caller for Argo CD. This distinguishes it from sibling tools that perform specific operations (e.g., get-application, list-applications). However, the schema allows mutation methods, causing some confusion.

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 says 'Mutations are blocked while ARGOCD_READ_ONLY=true', implying it's for read-only operations, but it does not provide explicit guidance on when to use this tool versus sibling tools like get-application or list-applications. No alternatives or exclusions are mentioned.

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