list_ads

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

No annotations are provided, so the description carries full burden. It discloses pagination parameters and defaults but does not mention ordering, whether it returns active/archived items, rate limits, or error behavior. This is adequate but incomplete.

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 concise and well-structured: a bilingual title, a clear one-line summary, then an args list. No wasted words or redundancy.

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 the tool has 4 parameters, no output schema, and no annotations, the description covers parameters well but lacks behavioral context such as sorting, pagination iteration, or return format. For a list tool, this leaves some gaps.

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 0% (schema only has titles and defaults), so the description compensates well by explaining each parameter: advertiser_id (required), campaign_id (optional), page (default 1), page_size (default 20, max 100). It adds meaningful context 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 the verb 'list' and the resource 'ad creatives/ad creatives', specifies the scope 'under an advertiser account' with optional filtering by campaign. It distinguishes from siblings like 'get_ad_detail' (singular) and 'list_campaigns' (different resource).

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 ad creatives with optional filters but lacks explicit guidance on when not to use this tool or alternatives. Siblings like 'export_data' or 'get_ad_detail' exist but are not mentioned.

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