sdcloud_list_variable_zones

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

No annotations are provided, so the description must fully convey behavioral traits. It fails to mention that the tool is read-only, what the response structure is (list of objects), or any side effects. For a list tool, basic behavioral context is missing.

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 a single sentence with 12 words, efficiently conveying the core functionality. No unnecessary information is present, and the key points (list, optional operations) are front-loaded.

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 with optional parameters, no output schema), the description is largely complete. It covers the purpose and optional operations. However, it omits the response format (list of variable zone objects), which would be helpful for an agent expecting structured 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?

All five parameters have descriptions in the input schema, achieving 100% coverage. The description adds no additional meaning beyond those schema descriptions, so it meets the baseline but does not enhance clarity.

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 tool's action ('list variable zone objects') and optional features (pagination, filtering, sorting). It distinguishes itself from sibling tools like 'get_variable_zone' (single retrieval) and 'create_variable_zone' (creation).

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 does not explicitly state when to use this tool versus alternatives (e.g., for retrieving a single zone use 'get_variable_zone'). The usage is implied but lacks explicit guidance or exclusion criteria.

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