yd_wordstat_regions

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

The description mentions '2 quota units' as a cost, which is useful behavioral info. However, without annotations, it lacks details on permissions, output size limits, or whether the data is real-time or historical.

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?

Three concise sentences front-load the core purpose and cost, with no unnecessary words.

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?

The tool lacks an output schema, and the description does not explain the return format (e.g., region names, percentages). For a retrieval tool, this leaves users guessing about the response structure.

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 provides no additional meaning for the parameters beyond the schema. The 'devices' parameter lacks a schema description and is not addressed in the tool description, leaving ambiguity.

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 tool retrieves regional distribution of search queries for a keyword, which distinguishes it from sibling tools like yd_wordstat_dynamics (trends over time) and yd_wordstat_regions_tree (hierarchical regions).

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 on when to use this tool versus other wordstat tools or alternatives. The description does not mention prerequisites, limitations, or comparison with siblings.

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