meta_ads_analysis_suggest_creative

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

Discloses read-only nature ('does not create creatives') and cost implication of longer analysis windows. No annotations provided, but description compensates well. Lacks details on behavior when no data is available.

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?

Four sentences precisely convey purpose, example output, read-only guarantee, and follow-up action. No wasted words; front-loaded with the primary action.

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?

Given 3 parameters with full schema coverage, no output schema, and no annotations, the description sufficiently explains what the tool returns (ranked list with examples), its read-only nature, and the correct next step. It also differentiates from the large sibling set effectively.

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 100% with robust field descriptions. The tool description adds context for account_id fallback and period cost, but the schema already provides sufficient detail, so baseline 3 is appropriate.

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 uses a specific verb ('Generates') and resource ('creative-improvement suggestions for a Meta Ads campaign'), clearly differentiating from sibling creative creation tools by stating it is read-only and does not create creatives.

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?

Explicitly advises to 'Follow up with meta_ads_creatives_create* to materialize the suggestions after operator review', providing clear when-to-use and alternative guidance. Also states it is read-only, reducing confusion.

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