catastro_descargar_municipio

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

Without annotations, the description discloses side effects (builds local cache) and scope (no limit, GML official), but does not cover auth, rate limits, or return format. The context is helpful but not comprehensive.

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?

Three sentences deliver purpose, usage guidance, and parameter format without redundancy or filler.

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 foundational download tool with no output schema, the description covers the purpose, parameter semantics, and usage threshold. It doesn't describe return values or edge cases, but it is adequate for this operation's simplicity.

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 description explains that both provincia and municipio are numeric codes and gives a concrete example (Muxía: '15', '15053'), which adds meaning beyond the bare string schema. With 0% schema coverage, this is essential.

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 uses a specific verb 'Baja' (downloads) and resource 'parcelario INSPIRE completo del municipio', and explicitly defines its scope as foundational and for bulk operations, distinguishing it from sibling tools like catastro_parcela_local.

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?

It states 'Operación fundacional: el resto la da por hecha' and 'Cualquier operación sobre más de ~20 parcelas se resuelve aquí, nunca una a una', which clearly directs when to use this tool over per-parcel siblings.

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