search_advertiser_by_domain

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

Despite no annotations, the description discloses return values (advertiser info with fields and null for not found) and implies a read-only operation through the verb 'search'. It could be more transparent about potential errors or edge cases, but it covers the main behavioral aspects.

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 concise docstring with clearly separated Args and Returns sections. Every sentence adds value, and there is no redundancy or fluff.

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?

For a simple single-parameter search tool with an output schema, the description covers purpose, parameter format, and return value adequately. No additional context is necessary for an AI agent to invoke it correctly.

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 schema has 0% coverage for the 'domain' parameter, but the description adds significant meaning by specifying it is a website domain and providing examples ('nike.com', 'coinbase.com'). This fully compensates for the lack of schema description.

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 'Find an advertiser by their website domain,' which specifies the verb, resource, and search criterion. It distinguishes itself from siblings like 'search_advertisers' by focusing on domain-based lookup.

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 provides a clear context for when to use the tool (when you have a domain) and includes an example. However, it does not explicitly mention alternatives or when not to use it, though the purpose is sufficiently self-explanatory.

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