ads_list_ads

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the listing action and parameter descriptions, but fails to mention pagination behavior, default status filter, return format, or error handling. This leaves significant behavioral ambiguity.

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 extremely concise and well-structured, starting with the primary action and then listing arguments. Every sentence adds value without redundancy, making it easy for an agent to parse quickly.

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, the description covers the core purpose and key parameters, but it lacks details on return fields, pagination, or status filter options. Given no annotations and no output schema, the description is adequate but leaves gaps that could affect agent usage.

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 description adds meaningful context for parent_id by specifying the format (act_ for ad account vs campaign/adset ID) and for status_filter by clarifying it is an effective_status filter. However, the limit parameter is not mentioned in the description, and status_filter allowed values are not specified, so it is not a perfect compensation for the schema's 0% coverage.

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 it lists ads under an ad account, campaign, or ad set, with a specific verb and resource. This distinguishes it from sibling list tools like ads_list_campaigns and ads_list_adsets.

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 (list ads under a parent), but it does not explicitly discuss alternatives or when not to use it. There is no mention of sibling tools or exclusions, leaving usage guidance implicit.

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