azure_scan_gitops_security

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

Annotations are empty, so the description must fully disclose behavior. It does not state whether the tool is read-only, what permissions are required, or any side effects. The description merely lists vulnerability categories without behavioral context.

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 a single sentence with no fluff, but it could be structured to separate purpose from capabilities. Still, it is concise and front-loaded with the core purpose.

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?

No output schema is provided, and the description does not explain the return format or results. The optional 'format' parameter's impact is not clarified. The tool is moderately complex (4 parameters), but the description lacks completeness regarding output and prerequisites.

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 parameters are already documented. The description adds no extra meaning beyond the schema (e.g., does not explain what subscriptionId or clusterName implies). Baseline 3 is appropriate as the description does not augment parameter understanding.

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 tool detects Azure GitOps (Flux) vulnerabilities and lists specific vulnerability types. It distinguishes itself from sibling tools like azure_scan_aks_full and azure_scan_azure_devops by focusing on Flux-specific issues.

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?

No explicit guidance on when to use this tool versus alternatives. With many sibling tools, there is no mention of when not to use it or which scenarios are appropriate. For example, it does not clarify that this is for Flux-specific vulnerabilities, not general AKS security.

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