rollback_application

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions dry-run defaults for safety, which is useful. However, it doesn't disclose that this is a destructive/irreversible operation when dry_run=false, doesn't mention whether it restarts/restores state, and doesn't describe what the output/response looks like (despite having an output schema). For a mutation tool with zero annotation coverage, this is a significant gap.

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 compact at three sentences, front-loaded with the core purpose, and every sentence adds value (purpose, workflow hint, safety default). It could be slightly more structured but is appropriate in length and density.

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?

The description covers the primary workflow (get history → rollback) and safety default well. However, given this is a potentially destructive mutation tool with no annotations and 0% schema description coverage, it should provide more context: what happens during rollback, whether it's reversible, permission requirements, and what the return value indicates. The output schema helps somewhat but the behavioral risk of a rollback operation warrants deeper disclosure.

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%, meaning the description must compensate for parameter documentation. The description mentions revision_id ('rollback to a previous deployment revision' and the get_application_history workflow) and dry-run ('Defaults to dry-run mode'). However, it adds no meaning for 'name' (beyond what the schema property says) or 'instance'. It partially compensates but doesn't fully cover the parameters.

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 (rollback) and resource (application to a previous deployment revision). It distinguishes itself from sibling tools like sync_application and refresh_application by its rollback-specific purpose. It could slightly improve by clarifying it uses ArgoCD history, but the core intent is unambiguous.

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 explicit usage guidance by directing users to call get_application_history first to find revision IDs, and mentions dry-run mode as the default for safety. It doesn't explicitly state when NOT to use it versus alternatives like sync_application, but the workflow hint is valuable and the safety emphasis provides clear context.

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