yandex_wordstat_get_top

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

With no annotations, the description carries the full behavioral burden. It adds useful context by mentioning 'raw provenance' and 'normalized output,' but it does not explain what these mean, nor does it disclose constraints, rate limits, or side effects. For a read-only retrieval tool, this is adequate but not rich.

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 compact sentence with no filler. It front-loads the core action and immediately adds the distinguishing output detail, making every word earn its place.

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?

An output schema exists, so return values may be covered, but the description lacks operational context: no parameter format guidance, no usage conditions, no clarification of 'raw provenance.' An agent would need to infer critical input details.

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 description coverage is 0%, and the tool description does not explain any parameters. 'phrase' and 'regions' are somewhat self-explanatory from their names, but the expected format of regions and the meaning of 'num_phrases' are left undefined, forcing the agent to guess.

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 the specific operation ('Get Yandex Wordstat top requests') and characterizes the output as 'raw provenance and normalized output.' It clearly distinguishes itself from siblings like yandex_wordstat_dynamics and yandex_wordstat_regions by focusing on top requests.

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 the many alternatives. The description neither mentions exclusions nor suggests a context such as 'use when you need top query phrases for a given set of regions.'

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