yd_wordstat_regions_tree

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

The description discloses 'No quota cost', a key behavioral trait for an agent. It also implies a read-only operation. Although annotations are absent, the description handles transparency adequately for a simple tool.

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 two sentences, front-loaded with the core purpose, and contains zero unnecessary words. Every sentence earns 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?

For a zero-parameter tool with no output schema, the description provides sufficient context: what it returns (full tree with IDs), its cost (free), and its use case. It is 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?

There are zero parameters, so the baseline is 4. The description adds no parameter details because none exist, but this is appropriate since the schema already covers it fully.

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 'Get' and the resource 'full tree of Wordstat-supported regions with IDs'. It distinguishes this tool from siblings like 'yd_wordstat_regions' by specifying 'full tree', and from 'yd_regions_get' which serves a different purpose.

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 says 'Use to find region IDs for other Wordstat methods', providing clear context for when to use this tool. It does not mention when not to use it or alternative tools, but the usage guidance is direct and useful.

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