list_applications

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

No annotations are provided, so the description carries the full burden. The description notes it's a read/list operation returning matching applications, which is helpful, but it doesn't disclose return format, pagination, or whether it summarizes vs. returns full app details. For a list operation without annotations, it gives basic behavioral context but not rich detail.

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 sentences, efficient and to the point. The second sentence adds useful context about use cases but has minor redundancy ('overview of applications in a project' overlaps with filtering concept). No wasted words.

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 format is documented elsewhere. The tool has 4 filters forming a straightforward list query. The description covers purpose and use cases adequately but doesn't disclose behavioral traits like whether it returns all fields per app or a condensed summary, and doesn't mention the instance parameter's role. Adequate but not rich for a tool with no annotations.

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% — the schema has 4 properties (project, instance, sync_status, health_status) with inline descriptions, but the paraphrase field in schema is empty (meaning no generated descriptions). Actually, each parameter does have a 'description' field in the schema covering all 4 params. The tool description adds the filtering concept and gives examples of status values indirectly. With all params documented in the schema, the description adds marginal extra meaning about filtering intent.

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 the verb ('List') and resource ('ArgoCD applications') with optional filtering, and mentions use cases ('overview of applications in a project or find unhealthy/out-of-sync apps'). However, it doesn't explicitly distinguish itself from siblings, though the filtering by sync/health status helps differentiate from get_application (which fetches a single app).

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 gives implicit use cases ('get an overview', 'find unhealthy/out-of-sync apps') which communicate when to use it, but it doesn't explicitly state when NOT to use it or name alternative tools. Getting a single application's details would better use get_application, but this isn't stated.

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