Argocd List Applicationsets

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the description only needs to add context. It does add the returned field set (generators present, strategy, health, conditions), which tells the agent what a 'slim row' contains, but says nothing about pagination behavior despite limit/offset params.

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?

A single tight sentence with the verb and resource front-loaded and the output shape in a trailing parenthetical. Every clause carries information; nothing is padding.

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 read-only list tool with a full output schema and fully documented parameters, the description covers what is needed to select and call it. The only minor gap is that it doesn't acknowledge the pagination parameters or the null-filter defaults, though the schema handles those.

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 100%, so all five parameters (limit, offset, projects, selector, appset_namespace) are already documented in the schema. The description adds no filter syntax or behavioral detail beyond that, so the baseline of 3 applies.

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 pairs a specific verb ('List') with the exact resource ('ApplicationSets') and adds a scoping detail ('slim rows') that signals a lightweight listing rather than a full fetch. It implicitly distinguishes itself from argocd_get_applicationset (singular) and argocd_generate_applicationset, but never names an alternative explicitly.

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 argocd_get_applicationset or argocd_generate_applicationset, and no mention of prerequisites or filtering context. The 'slim rows' phrasing implies a lighter-weight browse use case, but that is inference rather than guidance.

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