Browse Targeting Categories

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows it is a safe, read-only operation. The description adds minimal behavioral context—'all available' implies a complete enumeration but doesn't mention pagination, response format, or error behavior. With annotations covering the safety profile, the description adds some value but not enough for a higher score.

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 short and to the point, fitting within a line or two. However, the 'Args:' section is redundant with the schema and only covers one parameter inaccurately; it doesn't front-load the most critical behavioral info (what the tool returns). It's concise but not optimally structured for an agent.

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?

As a read-only browse tool with no output schema, the description should explain the returned data format and any caveats (e.g., pagination, localization). None of that is present. The description only states the purpose and one parameter, leaving an agent uncertain about what to expect from the call. This is inadequate for a tool with three parameters and no output schema.

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 67%, so the description should compensate for the undocumented 'type' parameter. It lists the category types, but incorrectly includes 'adlanguage' which is not in the schema enum (adTargetingCategory, adcountry, adlocale). This mismatch could mislead an agent. Additionally, it says nothing about 'class' or 'response_format', leaving two parameters without added context. The description does not fully compensate for the schema gaps.

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 action ('Browses all available targeting category types') and the resource (targeting categories for ad targeting). It distinguishes from the search tools by using 'browse' terminology, though it doesn't explicitly name an alternative. Sibling differentiation is implied but not explicit, so a 4 is appropriate.

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?

There is no explicit guidance on when to use this tool versus the search variants (e.g., meta_search_targeting_interests). The description only mentions 'for ad targeting' without specifying when browsing is preferred over searching or when to use the type parameter. This is a significant gap for selection.

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