Calcular Demanda Acs Cte He4

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description largely restates that ('Operación analítica de solo lectura') while adding that no local files or records are altered. It adds the dependency on cold-water network temperature derived from the province, which is useful, but omits any error conditions, table-lookup limits, or fallback behavior.

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 header-based structure (purpose, cuándo usar, comportamiento) is front-loaded and easy to scan. It is slightly padded by restating the read-only nature already covered by annotations, but no sentence is wasted enough to hurt readability.

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?

With an output schema present, the description need not explain return values, and it covers purpose, invocation context, and side-effect profile adequately. The one residual gap is the relationship between the two occupancy parameters (personas vs dormitorios), which is left to the schema.

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 all four parameters are already documented. The description adds only indirect meaning by mentioning the cold-water network temperature (tied to 'provincia') and the 60 °C output target; it does not clarify when to supply numero_personas versus numero_dormitorios, so it stays at the baseline for high-coverage schemas.

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 precise verb and resource ('Calcula la demanda normativa obligatoria de ACS'), pins the output unit and condition (60 °C, litros/día), and names the governing standard (CTE DB-HE4). No sibling tool covers ACS demand, so the agent can identify it unambiguously from the name-plus-description alone.

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 gives a clear context: determining the regulatory daily ACS volume for sizing thermal production and solar coverage installations in CE3X. It does not name alternatives or exclusions, but no sibling overlaps this calculation, so explicit routing is largely unnecessary.

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