manage_gitops

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

Annotations declare destructiveHint=true and openWorldHint=false. The description adds behavioral context by detailing each action's effect (e.g., 'sync triggers deployment', 'suspend disables auto-sync'). No contradictions. It does not cover auth or rate limits, but the destructive nature is well conveyed through action descriptions.

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 (≈100 words), front-loaded with purpose, and structured logically: general statement, then actions per tool, then a note about 'kind'. Every sentence adds necessary information without redundancy.

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 12 parameters, no output schema, and two tool variants, the description covers all actions, tool-specific behavior, and the requirement for 'kind'. It lacks return value details, but with no output schema, this is acceptable. The description sufficiently enables an agent to understand and invoke the tool.

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 baseline is 3. The description adds value by grouping actions by tool and explaining the purpose of 'kind' for FluxCD, which goes beyond the individual parameter descriptions. This semantic grouping aids selection.

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 it performs operations on GitOps resources (ArgoCD or FluxCD), lists specific actions per tool, and distinguishes between them. The verb 'operate' combined with resource types and action lists provides a precise, differentiated purpose from sibling tools like get_resource 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?

The description explicitly lists which actions belong to ArgoCD vs FluxCD and notes that the 'kind' parameter is required for FluxCD. It implies when to use this tool (for managing GitOps resources) but does not explicitly state when not to use it or refer to alternatives. However, the clear action sets guide appropriate usage.

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