catastro_parcela_local

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

No annotations are provided, so the description must carry the full transparency burden. It discloses the exact data source (areaValue del GML, the only accepted source), the outputs (centroid and geometry), and the cache/network behavior. However, it omits details about potential errors, cache staleness, or what happens if the cache is not populated.

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 a single, compact sentence that front-loads the core outputs and key behavioral constraints (cache, no network). Every word contributes value, with no 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 simple 1-parameter readonly lookup, the description covers the essential return values (area, centroid, geometry), the authoritative source (GML areaValue), and the network behavior. It lacks an output schema but explicitly lists what the tool returns. Minor gaps around error handling and cache availability prevent a perfect score.

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 input schema already fully describes the single parameter 'rc' with the constraint 'referencia catastral de 14 o 20 caracteres', giving 100% coverage. The description adds no extra semantic detail about the parameter, so the baseline 3 is appropriate.

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 returns 'Superficie oficial (areaValue del GML — la única fuente aceptada), centroide y geometría' from cache without network. It identifies a specific resource (parcela_local) and its outputs, but does not explicitly contrast with sibling tools, relying on the cache/network distinction to imply differentiation.

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 phrase 'desde caché, sin red' implies this tool is intended for situations where network access is unavailable or cached data is preferred. However, there is no explicit guidance on when to use this tool versus siblings like catastro_ficha or catastro_por_coordenada, nor any stated exclusions or prerequisites.

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