List ImotAI districts for a city

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

With no annotations, the description carries the full burden, and it does disclose a genuine data-completeness caveat: counts exist only 'where a public price page exists', and results are limited to cities ImotAI has data for. It does not state the read-only nature, error behavior for unknown cities, or ordering, so some behavioral gaps remain.

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 sentences, zero filler, front-loaded with what is returned before the call-first guidance. Every phrase ('where a public price page exists', 'in a given city') carries information.

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 one required parameter, no annotations, and no output schema, the description covers both return content (districts plus active-listing counts) and usage context adequately. Minor gaps remain on response shape details and unknown-city behavior, but nothing essential to calling it correctly is missing.

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 100% and the single 'city' parameter already documents slug vs Bulgarian-name formats, so the description adds no parameter-level detail. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb (List) and resource (districts/neighbourhoods) scoped to Bulgarian cities where ImotAI has data, and clarifies what each entry contains (listing counts). The framing as a prerequisite for 'the other ImotAI tools' separates it from search_properties, get_property and get_market_stats without ambiguity.

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?

Explicitly instructs 'Call this first to learn which "district" values are valid for the other ImotAI tools in a given city', which is concrete ordering guidance and a clear rationale. It stops short of stating when not to call it or naming the specific downstream tools, so it is strong but not exhaustive.

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