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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is fully covered and the description needn't restate it. The description adds only the filter capability; it says nothing about pagination behaviour, total counts, or how many records a caller should expect, which is the remaining behavioral gap.

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?

A single front-loaded sentence with no filler; appropriately sized for a simple list operation. It is efficient but bordering on under-specified rather than maximally useful.

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?

No output schema exists, so the description should say what a village record contains (at minimum an id usable with wilayah_get_kelurahan) and how paging works. Given 3 parameters with one-third schema coverage and a hierarchical data model, the one-line description leaves too much for the agent to guess.

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 only 33%: kecamatan_id is documented in the schema and merely restated in the description, while page and per_page have no descriptions anywhere, and per_page's maximum of 100 is never explained. The description does not compensate for the undocumented pagination parameters.

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 gives a specific verb ("List") and resource ("villages"), plus the optional filter dimension (district id), so an agent knows what comes back at a glance. It doesn't distinguish itself from nearby siblings such as wilayah_get_kelurahan (single record) or wilayah_search, so the agent must infer that this is the bulk-enumeration variant.

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?

Usage is implied by the word "List" and the "optionally filtered" phrasing, i.e. use it to enumerate villages under a district. There is no explicit when-not condition and no pointer to alternates like wilayah_get_kelurahan for detail or wilayah_search for name lookup.

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