Predicción diaria

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

With no annotations provided, the description carries the disclosure burden. It discloses the type of data returned (temperature, sky, precipitation, wind) and the scope (Spanish municipality, up to 7 days). It does not disclose error handling, data source, or update frequency, but for a read-only forecast tool this is acceptable, though not rich.

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, concise sentence that front-loads the core purpose and key output variables. It is appropriately sized and contains no waste.

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?

The description covers the main return values and the scope, while the schema provides detailed parameter semantics. Although there is no output schema, the description's enumeration of output variables (temperatura, estado del cielo, precipitación, viento) gives a clear picture of what to expect. It lacks explicit mention of response structure, but this is not critical for a straightforward forecast tool.

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 covers 100% of parameters with detailed descriptions, including examples and guidance for 'municipio' and the 1-7 range for 'dias'. The description's mention of 'hasta 7 días' and 'municipio español' adds no additional meaning beyond what the schema already provides.

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 provides a daily weather forecast for a Spanish municipality, including specific variables (max/min temperature, sky condition, precipitation probability, and wind). The word 'diaria' (daily) and the listed variables distinguish it from siblings like prediccion_horaria and observacion_estacion.

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 implies usage for daily forecasts up to 7 days, and the 'diaria' label makes the temporal scope clear. The parameter schema explicitly advises using buscar_municipio for ambiguous municipality names, which is a useful guideline. However, the description itself does not directly mention when to choose this tool over prediccion_horaria or other alternatives.

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