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 pagination and filter scoping, but says nothing about result ordering, whether matches are fuzzy or exact, what happens with an empty query, or whether codes vs. names are returned — significant gaps for a 6-parameter search 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?

Two short lines with no filler, and the core capability is front-loaded before the usage hint. Slight redundancy in listing filters that the parameter names already convey.

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 no annotations, no output schema, 6 parameters, and 0% schema coverage, the description is too thin for the tool's complexity. It never describes what a result record contains (names, codes, hierarchy level) or how pagination interacts with filtering, which an agent needs to call it competently.

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%, so the description must compensate and only partly does: it names region/district/community filtering and pagination, mapping loosely to region_code, district_code, community_code, limit, and offset. It adds no syntax hints (e.g. code formats, defaults, max limit) and says nothing about the required 'query' parameter's matching behavior.

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 specific verb and resource ('Пошук територій України') and enumerates scope: administrative names, oblast/district/community filters, and paginated output. It positions itself as the richer variant versus the bare search_territories sibling, though it never names that sibling 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?

'Використовуй для розрізнення однойменних населених пунктів' gives one concrete use case, so usage is implied rather than absent. However, with siblings search_territories, list_territories, and get_territory present, it never says when to prefer this tool over those, leaving the agent to infer the trade-off from the word 'detailed'.

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