reports_keywords_in_adgroup

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

No annotations are provided, and the description carries the full burden of behavioral disclosure. It fails to mention that the tool is read-only, required permissions, rate limits, or any side effects. The description is entirely silent on behavioral traits.

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, front-loaded sentence with no fluff. It is concise and to the point, though it could be expanded slightly to include more useful context without becoming verbose.

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's complexity (12 parameters, nested objects, no output schema), the description is severely incomplete. It does not explain the output format, required parameters, or how to use the selector. An agent cannot fully understand the tool's behavior or prerequisites from this description alone.

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 description coverage, the baseline is 3, but the description adds no additional meaning beyond the schema. Parameters like campaignId, adGroupId, and endTime lack description in both schema and description. The description does not explain the report output or how parameters affect results.

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 it is a keyword report scoped to a single ad group, which is a specific verb+resource combination. It distinguishes from sibling tools like reports_keywords_in_campaign (campaign scope) and reports_search_terms_in_adgroup (search terms, not keywords).

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 is provided on when to use this tool versus alternatives. It does not mention conditions for use, exclusions, or related tools, leaving the agent without context for proper selection.

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