ako_sync_diff

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the description does not need to repeat. It adds value by specifying that it shows 'specific inconsistencies' and the target resources (K8s Ingress/Service vs AVI VS/Pool). No contradictions.

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 extremely concise: one line for purpose, one for usage, and one for args. Every sentence earns its place with no wasted words.

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 tool has a single optional parameter and an output schema (not shown). The description covers the core functionality (drift identification) and parameter. It does not specify scope (e.g., namespace), but that is acceptable given the simplicity and presence of output schema.

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?

The single parameter 'context' has a schema title but no description (0% coverage). The description adds 'K8s context name (optional),' which clarifies its meaning adequately for such a simple parameter. This compensates for the missing schema description.

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 names the tool as a read operation that shows specific inconsistencies between K8s Ingress/Service definitions and AVI Controller VS/Pool objects, and explicitly states its purpose: 'Use to identify drift.' This distinguishes it from siblings like ako_sync_status (general status) and ako_config_diff (config diff).

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 provides clear usage guidance: 'Use to identify drift.' While it does not explicitly list when not to use or name alternatives, the sibling list implies that for general sync status or config diffs other tools are appropriate. The guidance is sufficient for a simple tool.

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