Get a Meta ad's review status

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

Annotations already mark the operation as readOnly and idempotent, so the safety profile is covered. The description adds the behavioral clue that rejection reason is only returned when applicable, but it does not disclose other useful context such as possible status values, invalid ad_id behavior, or response shape.

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 a single focused sentence with no filler. It front-loads the main purpose and adds one useful detail ('rejection reason if any') that goes beyond the title.

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 one-parameter read-only getter with strong annotations, the description covers the core return concept: review status plus optional rejection reason. It is slightly thin on output details since there is no output schema, but nothing critical seems missing for basic invocation.

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%, and the description does not explain the ad_id parameter's format, source, or semantics beyond the resource phrase 'an ad'. The schema only provides the name and type, so the agent gets little help understanding what values are valid.

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 action ('Get') and the resource ('an ad's review status'), including the additional detail that rejection reason is returned when present. It does not explicitly differentiate from sibling tool meta_ads_list_ads_by_status, which lists ads by status, but the singular focus on a single ad's status is reasonably clear.

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 the tool is used when you need a specific ad's review status or rejection reason, but it gives no explicit 'when to use vs alternatives' guidance. There is no mention of prerequisites, limitations, or when to prefer sibling status-related tools.

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