vast42_list_ads

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

With no annotations provided, the description is the sole behavioral disclosure. It only states 'List all' without revealing default limit, maximum results, pagination behavior, read-only nature, or any side effects. This leaves the agent to infer critical behavioral details from the schema and tool name.

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 that front-loads the verb 'List' and directly names the resource. There is no filler, and every word contributes to the core purpose.

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 with only two documented parameters, but the description lacks context about return format, default pagination, and how it relates to the many sibling ad-item tools. Since there is no output schema, this is a moderate gap in completeness.

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 already documents both parameters (limit and offset) with clear descriptions, so coverage is 100%. The tool description adds no parameter-level meaning beyond what the schema provides, earning the baseline score 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 the specific verb 'List' and identifies the resource as 'VAST 4.2 ad items', clearly distinguishing it from single-item retrieval tools like vast42_get_ad. However, the word 'all' could mislead since the schema includes pagination parameters (limit, offset), implying it does not necessarily return every item in one response.

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 usage guidance is provided. The description does not mention when to choose this tool over alternatives such as vast42_get_ad, vast_list_ad_items, or other list tools, and it offers no exclusions or context about its role in the broader workflow.

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