List YouTube ads

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

With no annotations, the description carries the full burden of behavioral transparency. It discloses that the tool filters for active and non-reported ads, requires authentication, and is available on free accounts. While it does not explicitly state that it is read-only or mention pagination, the 'Returns' verb implies a read operation, and the provided details offer reasonable transparency.

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 highly concise, consisting of exactly two sentences. The first sentence presents the core functionality and filters, while the second adds a relevant access note. No unnecessary words or redundancy are present.

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?

For a simple list operation with no parameters and no output schema, the description provides sufficient context. It clarifies the ad type, the filters (active, non-reported), and the ownership scope. While it does not describe the response format, that information is not critical for understanding the tool's basic purpose.

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 tool has no parameters, so the baseline score is 4. The description does not need to explain any parameters and does not attempt to, which is appropriate given the empty schema.

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 explicitly states that this tool returns YouTube video ads, specifying both the resource type and the scope (owned by the authenticated user). It also includes filtering criteria (active, non-reported) which further clarifies its purpose and distinguishes it from sibling tools that handle other ad types.

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 mentions that it lists YouTube video ads and notes that free accounts can use it, which provides some usage context. It does not explicitly contrast with alternatives like list_banners, but the resource type is unambiguous enough that an agent would know when to select this tool over others.

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