vast_list_channel_zone_assignments

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

The description gives no behavioral details beyond the bare action. It doesn't mention pagination (despite limit/offset params), result ordering, or any read-only guarantees. With no annotations provided, the description carries the full burden and fails to disclose useful context.

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, front-loaded sentence with no wasted words. It is concise and immediately conveys the core action, though it may be too terse to be fully helpful.

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?

For a simple list tool with two pagination parameters and no output schema, one sentence might be minimally adequate. However, the description lacks mention of pagination behavior or what the returned items represent, leaving some ambiguity for an agent deciding whether this is the right call.

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?

Schema coverage is 100%, with both 'limit' and 'offset' having clear descriptions. The tool description adds no extra meaning to the parameters, so the schema does the heavy lifting, matching the baseline of 3.

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 uses a specific verb ('List') and resource ('VAST channel zone assignments'), clearly indicating the operation. It distinguishes itself from singular 'get' variants, though it doesn't explicitly contrast with the non-prefixed 'list_channel_zone_assignments' sibling.

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?

No guidance is provided on when to use this tool versus alternatives like 'vast_get_channel_zone_assignment' or the non-prefixed list. There are no exclusions, prerequisites, or contextual cues beyond the generic verb.

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