list_ads

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

No annotations are provided, so the description must carry the burden. It lists return fields (id, name, adset_id, creative, status) but omits behavioral details such as pagination (limit, after parameters exist), rate limits, or that this is a read operation. The description adds some value but leaves significant gaps.

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 two sentences, front-loaded with the purpose and key parameters. It is efficient but could add a note on output structure without hurting conciseness.

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 7 parameters, no output schema, and no annotations, the description is incomplete. It covers only filtering by IDs and return fields but ignores pagination, status filtering, and field selection. A more complete description would mention these capabilities.

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%, so the description must compensate. It explains the three ID parameters (ad_account_id, adset_id, campaign_id) but does not mention limit, after, effective_status, or fields, leaving 4 of 7 parameters undescribed. The explanation for the IDs is good but insufficient overall.

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?

Description clearly states 'List ads' and specifies the three filter options (ad_account_id, adset_id, campaign_id), distinguishing it from sibling tools like list_adsets or list_campaigns. The verb-resource combination is explicit and the scope is well-defined.

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 tells the agent to pass one of three IDs but does not provide guidance on when to use this tool over siblings like search_ads_library or get_ad. There is no explicit when-not or alternative suggestion.

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