Argocd Sync Application

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

Annotations already declare destructiveHint=true, so the description earns credit for explaining WHY it is destructive (prune and force can delete or recreate resources) rather than restating the hint. It also discloses the async behavior (returns the started operation, or the final one with wait=True) and the `applications, override` RBAC requirement for revision.

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, front-loaded with purpose and destructive rationale, with no filler. The 'Returns the started operation; with wait=True, the final one' sentence is slightly telegraphic but still earns its place by conveying async semantics.

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?

With annotations covering the safety profile, a 100%-covered schema, and an output schema for return values, the description supplies the missing pieces: destructive rationale, RBAC prerequisite, and operation lifecycle. It omits any precondition about the target app existing or the meaning of the default timeout, but nothing critical is 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 description coverage is 100%, so the schema already documents all 13 parameters including force, prune, and revision. The description adds only the RBAC permission for revision override, which the schema itself already states ('needs override RBAC'), so it contributes essentially nothing new. Baseline 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?

States a specific verb+resource ('Sync an application') and immediately qualifies it with the destructive semantics. It is clearly distinguishable in intent from siblings like argocd_rollback_application or argocd_terminate_operation, though it never names an alternative to route the agent.

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?

Usage is only implied: the note that wait=True returns the final operation hints at a relationship with argocd_wait_for_operation, and the RBAC note implies a prerequisite for revision override. There is no explicit when-to-use/when-not-to-use guidance or named alternative for sync vs rollback.

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