list_applications

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions pagination in returns, which is useful, but lacks critical details: whether this is a read-only operation, what permissions are required, how filtering logic works (AND/OR), error handling, or rate limits. The refresh parameter's effect is noted but not fully explained (e.g., consequences of forcing reconciliation).

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 efficiently structured with a clear purpose statement followed by organized 'Args' and 'Returns' sections. Every sentence adds value: the first sets context, and the bullet points concisely explain parameters and output without redundancy. It's appropriately sized and front-loaded for quick understanding.

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 5 parameters, 0% schema coverage, no annotations, and no output schema, the description does a decent job covering basics (purpose, parameters, pagination). However, it lacks details on behavioral aspects like error handling, authentication needs, and filtering logic, making it incomplete for safe and effective use by an AI agent without additional context.

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%, so the description must compensate by explaining parameters. It successfully documents all 5 parameters with brief semantics (e.g., 'Filter applications by project name'), adding clear value beyond the schema. However, it doesn't specify format constraints (e.g., regex for names) or default behaviors when parameters are omitted, leaving some gaps.

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 verb ('List') and resource ('applications in ArgoCD'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this listing tool from its sibling 'get_application_details', which provides detailed information about a single application, leaving room for potential confusion about when to use each.

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 provides no guidance on when to use this tool versus alternatives like 'get_application_details' for single applications or other filtering methods. It mentions filtering options but doesn't explain when specific filters are appropriate or what happens without them, offering minimal usage context.

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