list_edge_clusters

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

Annotations already indicate read-only, open-world, idempotent. Description adds the "result envelope" concept and the `truncated` check, which is valuable beyond annotations. 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?

Concise with a clear front-loaded [READ] label. Each sentence serves a purpose: listing, truncation warning, usage flow, parameter explanation. 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?

Given no output schema, description mentions the return envelope and `truncated` for pagination, but doesn't detail all fields in each cluster object. However, it provides enough context for an agent to use the tool effectively alongside sibling tools.

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 has one parameter with 0% schema description coverage. Description explains that `target` selects the NSX Manager from config and defaults if omitted, adding necessary meaning.

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?

Clear verb (list) and resource (edge clusters) with specific details (member count, deployment type). Distinguishes from siblings by explaining how it relates to other tools like get_edge_cluster_status and create_tier1_gateway.

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 states when to use this tool (first to get cluster_id) and what to do next (get_edge_cluster_status). Also warns about checking `truncated` and explains its role in building edge_cluster_path for Tier-1 gateways.

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