list_municipios

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

With no annotations provided, the description carries the full burden for behavioral disclosure, but it only states the basic action and filter. It omits details about result volume (~345 municipalities), pagination, or any potential side effects, leaving the agent without important behavioral context.

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?

One short sentence ('List municipalities, optionally filtered by region.') with no filler or redundancy. It is appropriately front-loaded, and every word earns its place for a tool of this simplicity.

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?

Given the tool's simplicity, one optional parameter, and an existing output schema, the description is adequate. However, it lacks any mention of related tools or output expectations, leaving minor contextual gaps that could confuse an agent choosing between list_municipios and search_municipalities.

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?

The schema fully documents the 'region' parameter (coverage 100%), so the baseline is 3. The description merely reiterates that filtering is optional, adding no new semantic meaning beyond what the schema already provides.

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 ('List') and resource ('municipalities') with an optional filter ('by region'), clearly conveying the tool's function. It doesn't explicitly differentiate from sibling 'search_municipalities' but the list vs search distinction is implicit.

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?

The description implies usage for retrieving municipality lists, optionally scoped by region, but provides no explicit guidance on when to choose this over search_municipalities or list_areas, nor any exclusion criteria. It gives a clear context but no alternatives.

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