list_vngs

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

No annotations provided, so description carries full burden. Discloses return behavior (compact vs full), parameter effects, and filtering options. Lacks mention of side effects or mutability, but as a read-only list operation, this is sufficient.

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?

Well-structured with purpose, behavior, and bulleted args. Some redundancy in verbose explanation (e.g., listing config items then saying 'Use when...'). Slightly verbose but not excessive.

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?

Complete for a list operation with 3 optional params and an output schema. Covers filtering, output format, and parameter details. No critical gaps given the tool's simplicity.

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?

Despite 0% schema coverage, description explains all three parameters in detail: ocean_id, account_id (with env var fallback), and verbose (with usage recommendations). Fully compensates for missing schema descriptions.

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?

Description clearly states it lists AWS Ocean Virtual Node Groups (VNGs/launch specs), with specific verb 'List' and resource. It distinguishes between compact and verbose outputs, which differentiates it from siblings like get_vng or filter_vngs_by_tag.

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?

Provides context for when to use verbose mode (analyzing settings, troubleshooting). However, does not explicitly state when not to use this tool vs alternatives like get_vng or filter_vngs_by_tag, so some guidance is present but not exhaustive.

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