Calcular Calificacion Energetica

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds some operational context (it reads CE3X reference databases and registers no persistence), but the central 'read-only, no file modification' claim largely restates the annotation. With annotations carrying the safety burden, this is a modest add rather than rich new disclosure.

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?

Front-loaded purpose sentence followed by clearly labeled 'Cuándo usar' and 'Comportamiento' sections. Efficient and well-organized, though the behavior block slightly overlaps the annotation and could be tightened.

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 read-only calculation tool with full schema coverage, annotations, and an output schema, the description covers purpose, routing, and side effects adequately. Nothing an agent needs to invoke it correctly appears to be missing, though it says little about required environmental inputs beyond the parameters.

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 description coverage is 100%, so the schema already documents all six parameters, including ACS/heating vectors and allowed tipología values. The description adds no syntax, ranges, or defaults beyond what the schema provides, so 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?

States specific outputs (demanda energética, consumo de energía primaria no renovable, emisiones de CO2, letras A-G) and the data source it leverages (CE3X Escala/Localidades.xml). An agent can immediately tell this is the pre-certification energy-rating calculator, distinct from the full-certificate generator named as a sibling.

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 'Cuándo usar' section explicitly names the alternative tool 'generar_certificado_completo' and the condition that selects this one (quick pre-qualification before producing the definitive documentary package). Explicit when-to-use with a named alternative is exactly what a routing agent needs.

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