get_edge_cluster_status

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. The description adds that it checks member health and overall status, which is consistent. However, it does not disclose additional behaviors like response format or error handling beyond what annotations imply.

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 with no wasted words: a one-line purpose and two bullet-point parameter explanations. It is front-loaded with the [READ] tag and immediately clear about the task.

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 the tool's simplicity (2 params, no output schema), the description adequately covers purpose and parameters. However, it omits details about return value structure, which would help an agent anticipate the output.

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 0% description coverage, so the description provides meaning: cluster_id is described as 'the edge cluster ID', and target as 'optional NSX Manager target name from config; uses default if omitted'. This adds value, though cluster_id could benefit from more detail.

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 verb 'check' and the resource 'edge cluster status (member health, overall status)', distinguishing it from sibling tools like list_edge_clusters (which lists clusters) and other get tools for different resources.

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 explains it reads status given a cluster_id, but does not explicitly state when to use this tool over alternatives like list_edge_clusters or provide guidance on prerequisites or context. The optional target parameter is noted.

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