meta_get_ads

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

There are no annotations, so the description carries the behavioral transparency burden. It does disclose the read-only nature via 'List' and the output fields, but it does not mention pagination behavior, the effect of the cursor/limit parameters, or what the default status filter is when statusFilter is omitted.

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 concise sentences with no filler. The main action and resource are front-loaded, and the second sentence directly states the return fields, making it easy to scan.

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 read-only list tool with five parameters and no output schema, the description covers the essential purpose, filter behavior, and return fields. The schema fills in pagination and parameter details, but a short note about pagination or default status behavior would make it fully self-sufficient.

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 80%, so the schema already documents most parameters. The description adds meaningful context only for the ad set filter and the returned status field, but it does not enrich limit, cursor, or statusFilter beyond what the schema provides.

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 states a specific action ('List ads'), a specific resource ('Meta ad account'), and the optional filter ('by ad set'), which distinguishes it from siblings like meta_get_adsets and meta_get_campaigns. It also enumerates exactly what is returned, leaving no ambiguity about the tool's primary function.

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?

No guidance is given about when to choose this tool over its alternatives, such as meta_get_adsets, meta_get_campaigns, or meta_get_creatives. The description implies a listing use case but never states exclusions or conditions like 'use this for ads, not ad sets'.

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