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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial beyond that: the unauthenticated 10-row cap, the requirement that offset be 0 when unauthenticated, the country gate where only DZ answers, the special Algiers circonscription administrative case, and the Larbaa no-post-office edge case.

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 return shape are front-loaded, but the definition is one long run-on sentence burdened with full legal citations (décret exécutif n° 91-306…, décret présidentiel n° 2000-45) that are hard for an agent to scan. The procedural detail is useful but packed rather than structured.

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 output schema, the description still conveys the return shape (daïras with communes, codes, names), the meta.sources and meta.total fields, pagination behavior, and the auth-dependent limits. For a filtered-list tool this is complete enough to invoke correctly.

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%, so the schema already documents every parameter including enums, defaults, and limits. The description restates wilaya (1 to 69) and q (accents ignored) but adds no new syntax or format detail, so the baseline 3 applies.

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+resource (list daïras of Algeria) and precisely what each row contains (communes with four-digit code and name). It is clearly distinguishable from siblings like list_communes, list_wilayas, and get_commune, and adds authoritative scope (553 daïras, 1,541 communes).

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 concrete filtering guidance ('filter by wilaya (1 to 69) and q, accents ignored') and constraints ('Without an API key, at most 10 rows', 'Algeria only'). It does not, however, explicitly name an alternative tool or state when to prefer a different sibling such as list_communes.

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