get_keyword_traffic_estimates

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

Annotations already declare readOnlyHint=true, so no contradiction. The description adds behavioral details: it provides a min..max bracket at the supplied max_cpc and match type, and mentions the output fields (clicks, impressions, cost, position). This adds value beyond the readonly hint.

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 concise with two paragraphs. The first sentence front-loads the core purpose, and the second paragraph provides usage guidance. Every sentence adds value without redundancy.

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 (6 parameters, 2 required), the presence of an output schema, and the annotations, the description provides sufficient context. It covers purpose, usage, and behavioral details, making it complete for an AI agent to select and invoke correctly.

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 100%, so all parameters are described in the schema. The description adds context about the bracket nature and the bid input, which helps understanding. However, it does not add detailed semantics beyond the schema descriptions.

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 verb 'estimate' and the resource 'keyword traffic', listing the specific metrics (clicks/impressions/cost/position). It also distinguishes itself from the sibling tool 'estimate_keyword_bids', providing differentiation.

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 explicitly states when to use this tool (to gauge search volume and likely spend before launching) and when not (when you want traffic at a bid you choose rather than first-page suggested bid). It names the alternative tool 'estimate_keyword_bids' and explains the difference.

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