direct_list_ads

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

With no annotations, the description carries full behavioral burden. It clearly states READ-ONLY, which is valuable, and hints at a nuance with 'ACCEPTED OFF may be pool, not ban', but this is vague. It omits behavior such as pagination, return format, auth requirements, or error conditions.

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 core sentence is concise and front-loaded, but the 'UNIFIED' clause consumes space without conveying clear meaning. The overall structure is acceptable but the cryptic jargon reduces effectiveness.

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 tool with no output schema and no annotations, the description is incomplete. It does not explain the return structure, how filters interact, or how to interpret the 'ACCEPTED OFF may be pool, not ban' behavior. An agent would likely need additional context to invoke it reliably.

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 only 25%, and the description adds minimal semantic value beyond naming the filters. It does not clarify that limit controls page size, how IDs are combined, or what 'project' values are valid beyond what the schema already states.

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 states a specific verb ('List') and resource ('ads') with clear filter dimensions (campaign_ids/adgroup_ids/project). This distinguishes it from sibling tools like direct_get_ad or direct_list_adgroups, and the READ-ONLY label further clarifies its non-mutating nature.

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 to use the tool (when you have campaign/adgroup/project identifiers to list ads), but it does not explicitly mention alternatives or exclusions. The cryptic 'UNIFIED: ACCEPTED OFF may be pool, not ban' adds no practical usage guidance and may confuse an agent.

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