manage_gitops

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

Annotations already include destructiveHint:true, which covers the destructive nature. The description adds semantic detail for each action (e.g., 'sync' triggers deployment, 'suspend' disables auto-sync) without contradicting the annotations.

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 composed of two dense sentences that pack all essential usage rules: scope, per-tool action lists, and kind requirements. There is no filler or redundant information.

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?

Given the tool's complexity (12 params, multiple action sets per tool) and lack of an output schema, the description covers core decision points like which actions are valid for ArgoCD vs FluxCD and when kind is required. It could mention return values, but that is not strictly required when no output schema exists.

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 descriptions cover all 12 parameters, but the description adds cross-cutting information: ArgoCD always uses Application kind, while FluxCD requires a kind parameter (kustomization, helmrelease, etc.). This relationship is not visible in the schema itself.

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 'Perform operations on GitOps resources (ArgoCD or FluxCD)' and enumerates action types for each tool, making it distinct from sibling management tools like manage_workload or apply_resource.

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?

It provides a clear scope (GitOps resources only) and differentiates actions by tool, which is sufficient context for selection. However, it does not explicitly mention alternatives or cases where another tool should be used instead.

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