get_ads

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

The description discloses key behaviors: it searches by name, decodes text content, returns a list with specific fields (format, date, content). No annotations were provided, so the description carries the burden and does so adequately, though it lacks details on error handling or authentication.

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 concise, front-loaded with purpose, and structured with Args and Returns sections. Every sentence adds value without redundancy.

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 only two simple parameters and an output schema present, the description fully covers what the tool does, its inputs, and output structure. It is complete for its complexity.

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 schema description coverage at 0%, the description fully compensates by explaining advertiser_name (with examples) and count (default, max). This adds significant meaning beyond the schema.

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 it gets ads for an advertiser by name, with decoded content. It distinguishes from sibling tools like get_ad_detail (single ad) and search_advertiser_by_domain (domain-based search).

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 explains how the tool works (searches by name, fetches creatives, decodes content) and when to use it. However, it does not explicitly state when not to use it or alternative tools, though the sibling context implies differentiation.

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