reports_search_terms_in_adgroup

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention that this is a read-only operation, that pagination or filtering is supported, or what data is returned. The description is too brief to inform the agent about important behaviors.

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 very concise (one sentence) but lacks essential details. It could be longer to include usage context and behavioral notes. It is not overly verbose, but it sacrifices completeness.

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 complexity of the tool (12 parameters, nested objects, no output schema), the description is insufficient. It does not explain the purpose of the report, how to interpret results, or any limitations. The agent would need to rely solely on the schema and context signals.

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?

With 58% schema coverage, the description adds no additional meaning beyond what is in the input schema. The parameter descriptions in the schema already explain usage, but the tool description does not highlight any critical parameters or constraints, leaving the agent to infer from the schema alone.

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 states it is a 'search-terms report scoped to a single ad group', which clearly identifies the resource and scope. It distinguishes from sibling tools like 'reports_search_terms_in_campaign' but lacks an explicit verb (e.g., 'get' or 'list'), slightly reducing clarity.

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 no guidance on when to use this tool versus alternatives. It does not mention when not to use it or reference related tools like 'reports_search_terms_in_campaign' or 'reports_keywords_in_adgroup'.

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