Find Wordstat regions

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

Annotations already establish that the tool is read-only, idempotent, non-destructive, and open-world. The description adds useful context that the lookup is local and supports exact or substring name matching, but it does not explain child expansion behavior, parent scoping, result limits, or what the output contains.

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 front-loaded sentence with no wasted words. It gets directly to the resource, locality, and matching mode.

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?

Because an output schema exists, the description need not explain return values. But for a five-parameter lookup tool with child-related and parent-related options, the description is too sparse: it leaves the agent unable to determine how include_children, children_depth, and parent_region_id affect behavior.

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 there are five parameters. The description clarifies only the query matching behavior (exact or substring); it says nothing about limit, include_children, children_depth, or parent_region_id, so most parameter semantics remain undocumented in both the schema and the description.

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 a clear verb and resource: find Wordstat region IDs. It also specifies local exact/substring name matching, which helps an agent understand what kind of lookup this is. However, it does not explicitly contrast the tool with sibling region tools such as wordstat_regions or wordstat_regions_tree.

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 gives no guidance on when to use this tool versus wordstat_regions, wordstat_regions_tree, or other siblings. It also does not state exclusions or prerequisites, leaving the agent to infer routing from the tool name alone.

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