buscar_municipio

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

Given no annotations, the description fully discloses behavior: token-based search (not exact match), return of province even if not requested, and empty list on no match. It also mentions specific examples to illustrate fuzzy matching.

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?

The description is concise with no extraneous information. It is structured with clear sections: purpose, usage context, parameter description, and return format. Every sentence adds value.

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 simple input (one required parameter) and presence of an output schema, the description covers all necessary aspects: why the tool is needed, how search works, what the return includes, and edge cases (duplicates, empty list).

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?

Input schema has 0% coverage for 'nombre', but the description defines it as 'nombre o parte del nombre del municipio a buscar' and explains token-based search, adding substantial meaning beyond the schema's default title.

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 clearly states the tool searches Spanish municipalities by name to obtain their ID, explicitly linking it to the sibling tool precios_carburantes. It distinguishes itself by detailing the token-based search and handling of duplicate names.

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 explicitly states when to use the tool (to get a municipality ID for precios_carburantes), provides examples of token-based matching, notes that province is always returned due to duplicates, and mentions the return format, giving clear usage guidance.

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