Analyze Competitor Ads

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

Annotations already communicate the safety profile (non-readonly, non-destructive, open-world, non-idempotent). The description adds research scope but does not disclose further behaviors like latency, data freshness, or side effects, so it provides only modest added transparency.

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 sentence, front-loaded with the action verb, and generally concise. The list of content areas is somewhat long but not wasteful, making it effectively sized.

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 tool appears complex with multiple parameters and no output schema. The description lists what the research includes, but omits parameter details and return structure, leaving partial gaps for an agent deciding whether to invoke it.

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 meanings of 'markets' or 'results_per_market'. Only 'one competitor' indirectly refers to the competitor parameter, so the description fails to compensate for the lack of parameter documentation.

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 ('Run') and resource ('deep Meta Ads research pass for one competitor'), and lists specific content areas (creative mix, CTAs, landing domains, localization, social metadata, longest-running ads), which distinguishes it from sibling tools like search_meta_ads.

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 use when deep, single-competitor research is needed, which provides clear context. However, it does not explicitly name alternative tools or include exclusion criteria, so it stops short of a 5.

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