yandex_wordstat_regions_tree

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

No annotations are present, so the description carries the behavioral burden. It does disclose that Cloud credentials are required and that a 'server budget gate' applies, which are useful constraints. However, it does not explain what the gate does, whether the call is read-only, or what failure behavior to expect.

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 short sentence with no filler and states the core resource up front. The phrase 'server budget gate' is jargon, but it does not make the description bloated.

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?

With an empty input schema and an output schema present, little structural information is missing. Still, the meaning of 'server budget gate' and the relationship to yandex_wordstat_regions are unclear, leaving the definition only minimally complete.

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 input schema is empty with zero parameters, so there is no parameter semantics to document. The description adds no parameter details, but none are needed; the zero-parameter baseline applies.

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 starts with 'Get the Wordstat region tree', a specific verb and resource, so an agent knows what the tool returns. However, it does not distinguish this from the sibling tool yandex_wordstat_regions; 'tree' implies a hierarchy but the difference is left implicit.

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?

There is no guidance on when to use this tool versus yandex_wordstat_regions or other Wordstat tools. The mention of 'Cloud credentials and the server budget gate' hints at prerequisites but does not explain when this tool is the right choice.

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