get_ads

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

Without annotations, the description adds meaningful behavioral details: it specifies that adset_id 'takes precedence over campaign_id' and includes the default limit of 50, implying pagination. It also lists valid values for status_filter, though it does not explicitly state that the operation is read-only.

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: a one-line summary followed by a list of parameters with clear labels. Every sentence adds information, no redundancy, and the structure is easy to parse.

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?

The description covers the 5 parameters well but omits the output format (e.g., list of ad objects with fields) and prerequisites (e.g., account access). Given that there is no output schema, the lack of return value description is a gap. Context from siblings is implied but not explicit.

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 0%, so the description must and does compensate. It explains each parameter: account_id format, campaign_id/adset_id as optional filters, adset_id precedence, status_filter valid values, and limit default. This adds significant meaning beyond the schema's type-only definitions.

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 'List ads for an account, campaign, or ad set.' It is specific about the resource (ads) and the scope (by account/campaign/ad set), distinguishing it from sibling tools like get_campaigns or get_ad_details which target different resources.

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 lacks any guidance on when to use this tool versus alternatives like get_ad_details or get_bulk_insights. No explicit 'use this when' or 'alternatives' are mentioned, leaving the agent to infer context solely from the name and parameters.

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