ako_ingress_diagnose

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

Adds behavioral context beyond annotations: details three validations, return content (annotations, issue list, fix suggestions), and next steps if clean. No contradiction with 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?

Concise (~140 words), well-structured with summary, body, parameters. No unnecessary sentences.

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?

Covers validations, output, and next steps. With output schema present, return values are covered. Minor omission: no mention of error cases beyond missing name.

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 0%, but description provides meaningful details for each parameter: name must be exact and returns 'not found', namespace defaults to 'default', context optional and discoverable via ako_clusters.

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?

Clearly states it diagnoses why an Ingress has no corresponding AVI Virtual Service, lists three validations, and distinguishes from sibling tools like ako_ingress_map and ako_ingress_check.

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?

Explicitly instructs to use ako_ingress_map first and then diagnose one here. Lacks explicit 'do not use for' but provides clear context.

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