Argocd Create Application

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so safety is covered. The description adds two pieces of non-obvious behavior: the return is 'slim' and it is 'Idempotent only with upsert=True' – both material to an agent deciding whether a retry is safe. It does not mention required permissions or side effects like auto-sync kicking off.

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?

Three short sentences, all front-loaded: what it does, the alternative, the return and idempotency semantics. Every sentence earns its place and no filler is present.

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?

Output schema exists, so return values need not be explained; the description still adds the key 'slim' qualifier. For a 22-param create tool with full schema coverage and annotations, this is nearly complete – only concrete prerequisites (project must exist, repo must be registered) are missing.

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%, so every parameter is documented in the schema. The description adds no per-parameter syntax, constraints, or format guidance beyond the schema. Baseline 3 is correct when the schema does all the heavy lifting.

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?

States a specific verb+resource: create an ArgoCD application, and clarifies the parameter style ('flattened parameters'), distinguishing it from the structured-manifest approach used by some siblings. It does not explicitly name argocd_patch_application or argocd_generate_applicationset, but the reference to 'patch for anything this does not cover' gestures at the sibling.

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?

Explicitly tells the agent when to use patch instead ('Use patch for anything this does not cover'), which is a real routing rule. It does not state prerequisites (project existence, repo credentials) or when not to use create at all, so it falls short of 5.

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