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

No annotations are provided, so the description must carry the full behavioral burden. It establishes the read-only nature ('List') and the auth requirement ('authenticated Vadyu account'), plus the coupling of export_format to video_ids, but says nothing about return shape, ordering, pagination metadata, or whether video_ids bypasses page/limit — significant gaps for a tool with no annotations and no output schema.

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?

A single front-loaded sentence with the core purpose first and the optional modes trailing in parentheticals. Dense but waste-free; only the doubled 'batch ... export' phrasing is mildly redundant.

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?

With five optional parameters and no output schema, the description should say what a listing returns and what export output looks like. It covers the input modes adequately but leaves return values, pagination metadata, and empty-result behavior entirely unspecified.

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?

Schema description coverage is 100%, so every parameter is already documented, which sets the baseline at 3. The description adds little beyond restating the parameter roles, though it does usefully frame video_ids as triggering an aggregation ('batch video_ids[] campaign export') rather than a plain filter.

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?

Opens with a clear verb+resource ('List generated video ads in the authenticated Vadyu account') and enumerates the three operating modes: status filtering, pagination, and batch export. It is distinguishable from vadyu_get_video_status by scope (account-wide list vs. single video), though no sibling is named explicitly.

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 implies when each capability applies (filter by status, page through results, or pass video_ids for batch export) but never states when to prefer this tool over vadyu_get_video_status for a single video. There are no explicit exclusions or preconditions beyond the authenticated-account requirement.

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