direct_search_geo_regions

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

No annotations are provided, so the description carries the full burden. It discloses that the operation is READ-ONLY and that search is by substring. However, it doesn't describe the return format, pagination, or any default behavior. The description adds some behavioral context, but not extensive detail.

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 main action, and every phrase adds value. No filler or redundancy.

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 dictionary search tool with no output schema and minimal annotations, the description covers the core purpose, read-only safety, and a usage hint. It lacks details about output structure or pagination, but these are less critical for a straightforward lookup tool.

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 67%, with 'query' and 'type' described in the schema. The description adds context by mentioning 'name substring' (aligning with query) and 'Federation subject IDs' (aligning with a type filter), but it doesn't clarify the 'limit' parameter. The description provides some additional meaning beyond the schema but not full compensation.

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 action: 'Search Yandex Direct GeoRegions dictionary by name substring.' This specifies the verb (Search), resource (GeoRegions dictionary), and method (by name substring), distinguishing it from sibling tools like direct_list_dictionaries or direct_set_region_excludes.

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 provides a clear context: it's a read-only search for GeoRegions, and it gives a specific use case ('Use Federation subject IDs for RegionIds excludes (negative)'). It doesn't explicitly mention alternatives or exclusions, but the guidance is useful for when to apply this tool.

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