List ads

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds no additional behavioral context beyond listing with filters; it does not disclose pagination behavior, return format, or any limits. With annotations covering safety, the description offers minimal added value.

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, concise sentence that immediately states the purpose and main filtering options. No wasted words, and the core action is front-loaded.

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 9 parameters, no output schema, and pagination features (limit, offset, autoPaginate), the description fails to mention that the tool returns a list of ads, how pagination works, or what the output structure looks like. The agent lacks crucial information to use the tool effectively beyond 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?

Schema coverage is 100% with all parameters having descriptions. The description mentions filtering by campaign, ad group, id, state, and status, which groups some parameters but omits others like limit, offset, fieldNames, and autoPaginate. It adds limited semantic value beyond the 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 clearly states 'Lists ads' with optional filtering, which is specific to the resource. However, it does not explicitly distinguish from sibling tools like list_ad_groups or list_campaigns, though the resource name 'ads' provides differentiation.

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 usage for listing ads with filters but offers no explicit guidance on when to use this tool versus alternatives like ad_action or create_text_ad. The context of sibling tools suggests many ad-related operations, but no when-to-use or when-not-to guidance is provided.

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