vast42_list_universal_ad_ids

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the basic action ('List all') and does not mention pagination behavior, default limits, return format, or any side effects (though listing is inherently read-only). The verb 'List' implies a safe operation, but no additional behavioral details are given.

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 fluff. It is concise and front-loaded, efficiently stating the tool's purpose without unnecessary elaboration.

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?

Given the low complexity (2 optional params, no output schema), the description is adequate for a basic listing operation. However, it omits any mention of pagination behavior (despite limit/offset parameters), which could lead an agent to assume 'all' means all results in a single response. Lacks detail on response structure, but this is partially mitigated by the schema.

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 has 100% coverage: both 'limit' and 'offset' have descriptions. The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline score of 3 applies.

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 'List all VAST 4.2 universal ad IDs' uses a specific verb ('List') and a clear resource ('VAST 4.2 universal ad IDs'). It distinguishes this tool from siblings like vast42_get_universal_ad_id, vast42_create_universal_ad_id, etc., by clearly indicating a list operation.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention that this should be used for listing as opposed to retrieving a single item (vast42_get_universal_ad_id) or for creating/updating/deleting. No context about typical use cases or exclusions is provided.

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