search_ads

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

With no annotations, the description carries full burden. It discloses return contents (creatives, platform, images, URLs, date ranges) but does not state that the tool is read-only, mention pagination behavior, rate limits, or authentication requirements. Some gaps remain, but the core behavior is moderately transparent.

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 two sentences: first states purpose and filters, second states return content. Efficient, front-loaded, and no wasted words.

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 6 optional parameters, no output schema, and 14 sibling tools, the description is adequate but incomplete. It lacks details on default sort, pagination behavior, and differentiation from related tools. It does not mention prerequisites or if the tool is read-only.

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?

The input schema covers all 6 parameters with descriptions (100% coverage), so the baseline is 3. The description mentions 'keyword' and 'store_domain' but adds no new meaning beyond the schema. It provides context on return fields but not on how parameters affect results.

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 verb 'Search', the resource 'e-commerce advertisements', and the scope 'across platforms'. It lists filtering options and return fields, making the tool's purpose specific and distinct from siblings like 'get_ad' (singular) or 'search_stores'.

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 does not provide any guidance on when to use this tool versus alternatives such as 'get_store_ads' or 'get_ad'. It only implies usage for filtering by keyword or store domain, but no explicit when-to-use or when-not-to-use information.

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