vast_get_zone

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

No annotations are provided, so the description carries the full burden. The verb 'Get' strongly implies a read-only operation, but the description discloses no error behavior, response format, or authentication requirements. It is minimal but not misleading.

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 short sentence, front-loaded with the core purpose. No redundant or filler content.

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 simple, but the description omits key context: it does not clarify that it applies to active zones as opposed to archived ones (vast_get_archived_zone exists as a sibling), and with no output schema, it doesn't indicate what 'details' are returned. It is minimally viable but leaves gaps.

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 input schema fully describes the only parameter `id` as 'VAST zone ID' (100% schema coverage). The description adds no extra meaning beyond saying 'specific VAST zone', which doesn't enrich the parameter semantics.

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 'Get details of a specific VAST zone' clearly identifies a retrieval operation for a single entity. It distinguishes from sibling list tools (vast_list_zones) and mutation tools (vast_create_zone, vast_update_zone).

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 word 'specific' implies this tool is for fetching one zone by ID, but the description provides no explicit guidance on when to use it vs alternatives like vast_get_archived_zone or vast_list_zones. No exclusions or alternative recommendations are given.

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