search_interests

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

Describes returned fields (id, name, audience_size) but does not disclose authentication needs, rate limits, or side effects. Since no annotations, more detail would help, but the read-only nature is implied.

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?

Two sentences, front-loaded with key action, no unnecessary words. Every sentence adds value.

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?

Describes output fields (id, name, audience_size) and usage context despite lacking parameter details. Output schema exists but is not detailed; description covers key return values.

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 0%, and description only hints at 'query' parameter (search by name). No explanation for 'limit' or 'account_id', so agent lacks guidance on their usage.

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?

Clearly states 'search targetable interests by name', specifying action and resource. Distinguishes from sibling tools like create_adset and get_ads by being a search/list operation.

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 says results are used to load into a flexible_spec interest stack on an ad set, giving context for when to use. Could mention when not to use, but adequate.

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