plan_list_voc_plans

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

There are no annotations, so the description carries the full behavioral disclosure burden. However, it only states 'List' and describes the output format, with no mention of read-only behavior, pagination, authentication needs, or any side effects. This leaves significant behavioral context unspoken.

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 and front-loaded with the core purpose, followed by clear sections for arguments and returns. Every sentence adds value, and there is no filler or irrelevant information. The structure is easy to parse.

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 is a straightforward listing operation with a single parameter and an output schema may be present in structured data. Given this low complexity, the description covers the essential aspects: it states what is returned and the parameter. It does not elaborate on the shape of VOC plans, but that is likely covered by the 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 description adds meaning to the sole parameter by explicitly documenting the 'format' options ('compact' default or 'json') and their meaning, which the schema (0% description coverage) does not provide. This compensates for the lacking parameter metadata, though it is terse.

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 states the verb 'List' and a specific resource 'VOC (Optimized Cloud) plans', which is clear. It is specific enough to distinguish from the foundational plan tools, though it does not explicitly name the sibling plan listers (e.g., plan_list_vc2_plans, plan_list_vhf_plans).

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 no guidance on when to use this tool versus alternative plan listing tools. It does not mention that this is one of several plan type specific listers, nor does it offer any when-to-use or when-not-to-use guidance.

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