list_vngs_azure

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

With no annotations, the description clearly explains the tool's behavior: compact summaries by default, verbose returns full configurations. It lacks disclosure of side effects or safety (e.g., read-only), but for a list operation this is sufficient. The parameter use is well described.

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 appropriately front-loaded and uses a clear structure with an Args section. Every sentence adds value, though it could be slightly more concise by merging some lines. Overall, it is efficient without waste.

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 (list operation with 3 params) and the presence of an output schema, the description covers the main behaviors: default vs verbose output, filter by ocean_id. It omits potential details like pagination or constraints on account_id, but is largely complete for common use cases.

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 schema had 0% description coverage, so the description compensates fully. It explains each of the 3 parameters: ocean_id for filtering by cluster ID, account_id for Azure account, verbose for full configurations. This adds significant meaning beyond the schema's type and title.

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 starts with 'List Azure Ocean Virtual Node Groups', clearly stating the verb and resource. It distinguishes from siblings like 'list_vngs' (likely for AWS) and 'get_vng_azure' (single VNG). The addition of default and verbose behaviors further clarifies the tool's purpose.

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 guidance on when to use the verbose parameter ('Use when analyzing VNG settings...'), but does not explicitly compare this tool to alternatives like 'get_vng_azure' or when not to use it. The usage context is implied rather than explicit.

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