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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description's real contribution is the note that HCP names douars in Arabic only and Latin forms are transliterated — meaning Latin queries work against Arabic-indexed data via romanization. That is genuine behavioral context an agent could not infer, though it omits anything about match fuzziness or ranking.

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?

Purpose and the example are well front-loaded, but the middle two sentences about HCP naming and how the Latin spelling is derived are dense ('is otherwise spelt from the Arabic, which spelt marks') and slow the agent down for little operational value. Roughly a third of the text is etymological explanation rather than call guidance.

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 two-parameter search with an output schema present, this covers what is needed: what is searched, in which scripts, what comes back (code, 2024 population, commune), and where to go next. The only gap is expected match behavior for partial or misspelled names.

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 coverage is 100%, so baseline is 3, but the description earns more: it explains that تشديرت and Tachdirt both resolve to the same douar, telling the agent the query field accepts either script and that transliteration is reconciled. It says nothing extra about the limit parameter, which the schema already documents.

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?

Opens with a specific verb+resource ('Find douars, the villages and hamlets of Morocco's rural communes') and immediately bounds it to name-based lookup, which cleanly separates it from get_douars, get_commune, and list_communes in the sibling set. An agent can tell what this does and what it is not for without opening the schema.

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 clear usage context (search by name in Arabic or Latin) and routes the agent forward: 'pass the commune's slug to get_douars for the douar's households and distances.' It does not state an explicit when-not (e.g., if you already have a code, use get_commune), so it stops short of a full 5.

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