list_video_creatives

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention pagination, response limits, scope (e.g., whether it lists creatives across all advertisers or a specific context), or any other behavioral traits beyond the bare act of listing. The word 'all' is vague and unexplained.

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, compact sentence with no unnecessary words, making it concise and front-loaded. It is not verbose, but its brevity also means it omits potentially useful context, keeping it from a perfect score.

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?

Despite the simple schema, the description leaves out important context: it does not explain what 'video creatives' refers to in this system, how pagination works (though it is implied by the schema), what the response contains, or how this tool relates to other creative listing tools. The absence of an output schema increases the need for description, which is unmet.

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 schema already provides descriptions for both parameters (limit and offset), covering 100% of the parameter space. The description adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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 operation ('List') and the resource ('video creatives'), making the basic purpose understandable. However, it does not differentiate this tool from closely related siblings such as 'list_creatives' or 'list_all_creatives', so it stops short of a perfect score.

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?

There is no guidance about when to use this tool versus alternatives like 'list_creatives' or 'get_video_creative'. The description only states the function without any contextual hints, exclusions, or alternative suggestions.

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