get_meta_ads

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

Given the readOnlyHint=true annotation, the description adds useful behavioral context beyond safety: it fetches only active ads, includes content/media/dates/targeting, and discloses that visual analysis requires a separate tool. It does not contradict annotations.

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 three sentences with front-loaded purpose, no redundancy, and each sentence adds essential information about usage and limitations.

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 core purpose, usage sequence, output fields, and a key limitation. However, it omits explanations for optional parameters and does not describe the return structure in detail, which is more critical given the lack of an output schema.

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?

With 0% schema description coverage, the description must compensate but only explains the required platform_ids parameter. The optional parameters trim, limit, and country are not described, leaving their meaning unclear.

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 'Retrieve currently running ads for a brand using their Meta Platform ID,' identifying the action, resource, and scope. It distinguishes itself from sibling tools like get_meta_platform_id and analyze_ad_image by explicitly naming them.

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?

It provides explicit usage guidance: 'Use this tool after getting a platform ID from get_meta_platform_id' and directs users to 'MUST also use analyze_ad_image on the media_url' for visual analysis, covering both workflow and complementary alternatives.

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