zernio_get_ad_interests

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

No annotations are provided, so the description bears the full burden. It states 'Browse' implying a read operation, but does not disclose any behavioral traits such as pagination, authentication requirements, rate limits, or what happens with an empty query. The description is too minimal for 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 that is front-loaded and contains no superfluous information. It is efficient, though could benefit from slightly more structure.

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 the tool has one parameter and no output schema, the description is incomplete. It does not explain the return format (e.g., list of interest strings or objects), how the query parameter works, or how to handle results. The description leaves gaps for an AI agent to effectively use the tool.

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?

There is only one optional parameter 'query' with schema description 'Search query to filter interests'. The tool description does not add any additional meaning beyond what the schema already provides. With 100% schema coverage, the baseline is 3, and no extra value is added.

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 tool browses available interest targeting options for ads, listing examples like hobbies, demographics, behaviors. It is specific to ad interests, distinguishing it from many sibling tools that deal with other entities, but it does not explicitly differentiate from other 'list' or 'get' tools.

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?

No guidance on when to use this tool versus other similar tools like 'list_audiences' or 'get_ad'. No exclusions, prerequisites, or context for use cases are provided.

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