search_terms_report

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

No annotations are present, so the description carries the full transparency burden. It states a read-like action ('Get') but does not disclose limitations, data freshness, or whether results are historical or real-time. The row_limit and default are only in the schema, not in the description.

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 10-word sentence with no filler. It delivers the core message immediately and is appropriately terse for a simple reporting tool.

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?

Despite having an output schema, the description is incomplete for a tool with 3 required parameters and optional filters. It leaves out any discussion of date ranges, filtering, or typical use cases. The absence of sibling differentiation further reduces its completeness for an agent's decision-making.

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 description adds no information about parameters beyond what the schema already provides. It does not clarify the date format or the meaning of start_date/end_date, which are undocumented in the schema. The only parameter-related insight, 'your ads,' is too vague to be useful.

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 'Get actual search terms that triggered your ads' uses a clear verb and resource. It explicitly says 'actual search terms' which differentiates it from sibling tools like get_keyword_performance or get_ad_performance, making the tool's purpose unmistakable.

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 mention when to use this tool vs alternatives such as get_keyword_performance or get_ad_performance. There is no 'use this when' or 'instead of' language. The agent is left to infer that this tool is for search-term (query) reporting, but no explicit guidance is provided.

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