set_ayuntamiento

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

With no annotations the description carries the full burden, and it does disclose the effect scope (the active municipality applies to queries and incidents), which is real behavioral context. However, it is silent on persistence across sessions, permission requirements, and what happens with an invalid ID.

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?

A single front-loaded sentence with zero waste; the action and its effect are stated immediately.

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 one-parameter state-setting tool with no output schema, the description covers the essential purpose. It omits the practical prerequisite of sourcing a valid ayuntamientoID (e.g., via list_ayuntamientos) and any persistence/error behavior, leaving modest gaps.

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 single parameter ayuntamientoID is already documented in the schema with an example value. The description adds nothing beyond the schema, so the baseline 3 applies.

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 a specific verb and resource: 'Cambia el ayuntamiento activo' (changes the active municipality). An agent can tell it is a setter of session context, distinct from the sibling list_ayuntamientos which enumerates them. It does not explicitly name a sibling to differentiate against, keeping it short of a 5.

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?

'para las consultas e incidencias' implies the change scopes subsequent queries and incident calls, which is implicit usage guidance. There is no explicit when-to-use, no note that the ID should first be obtained from list_ayuntamientos, and no when-not-to-use.

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