vast42_list_non_linears

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

The description only states the operation without disclosing that results are paginated via limit/offset, with a default max of 100, so the claim 'List all' is potentially misleading. There are no annotations to convey side effects, so the description should explain behavior but does not.

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, focused sentence with no filler. It efficiently states the tool's purpose, though it could provide more context without being verbose.

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 has a two-parameter schema and no output schema or annotations, requiring the description to cover return values and behavioral details. It provides neither, leaving the agent unaware of the paginated response structure and default limits.

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 both limit and offset with clear descriptions, so the baseline is 3. The description adds no additional meaning beyond the schema, but that's acceptable given schema coverage.

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 identifies the action (List) and resource (VAST 4.2 non-linear media), distinguishing it from single-item getters and other media types. However, it does not differentiate from similar list tools like vast_list_non_linear_media, relying mostly on the version prefix.

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 explicit guidance is provided about when to choose this tool over alternatives such as vast42_get_non_linear for a single item or vast42_list_linears for linear media. The context implies it is the listing endpoint for non-linear media, but pagination behavior and use cases are not mentioned.

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