xmlstock_wordstat_regions_tree

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

Only mentions that requests are paid. With no annotations, the description should disclose more behavioral traits (e.g., read-only nature, rate limits, authentication). The cost note is useful but insufficient.

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?

Single, front-loaded sentence with no redundant words. Every part adds value: what it returns, how it's used, and cost.

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?

For a simple one-parameter tool without output schema, the description covers the essential output and usage context. Could mention format or limitations but not critical.

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% and already describes the single parameter 'account'. The description adds 'ПЛАТНО за запрос' but not additional semantics beyond the schema. Baseline 3 is appropriate.

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 returns a tree of Yandex Wordstat regions with id, name, and path, and that the id is used as a region parameter in other requests. It distinguishes from sibling xmlstock_wordstat_regions by emphasizing 'tree' (hierarchical), though not explicitly.

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 alternatives like xmlstock_wordstat_regions or other siblings. Does not specify prerequisites or context for using the region IDs.

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