vast42_list_creatives

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

No annotations are present, and the description only states 'List all VAST 4.2 creatives' without clarifying pagination limits, return structure, or whether the list includes archived items. The word 'all' may mislead an agent into thinking the response is unbounded, when the schema clearly limits results to 100. There is no mention of the read-only behavior, though 'list' implies it.

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 no filler, which is appropriate for a straightforward list operation. However, it is so brief that it under-specifies key behavioral aspects, balancing conciseness at a 4.

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 lacks an output schema and annotations, and the description gives no information about response format or pagination behavior. The presence of limit/offset parameters is not explained in the description, making it incomplete for an agent to understand how to properly iterate over results. Sibling tools like vast42_list_ads also have richer context (if they had descriptions) but here the tool is relatively simple.

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 provides complete descriptions for both parameters (limit and offset), so the description adds no additional parameter semantics. With 100% schema coverage, the baseline of 3 is applied.

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 verb 'List' and specifies 'VAST 4.2 creatives' as the resource, making the operation unmistakable. It distinguishes itself from sibling vast42 list tools (e.g., vast42_list_ads, vast42_list_linears) by the entity type, but does not differentiate from the generic list_creatives tool despite the VAST 4.2 qualifier.

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 given about when to prefer this tool over alternatives like vast42_get_creative for single items or list_creatives for non-VAST creatives. It also doesn't explain pagination usage despite the presence of limit/offset parameters. The context is only implied by the tool name.

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