Listando salas

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

With no annotations, the description carries the burden and does well: it discloses caching behavior (~15s first call, 30 min cache) and the return shape. It omits auth/permission requirements and error behavior, but the cache disclosure is meaningful behavioral context beyond the schema.

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-loads the main purpose, then uses Args/Devuelve sections for scannability. Content is dense but organized; a few phrases repeat the 'nombre EXACTO' filter guidance, slightly redundant but not wasteful.

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 two-param, no-output-schema tool, the description supplies the return structure, catalog sources, downstream filter usage, and caching latency. Nothing an agent needs to call it correctly is missing.

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 0%, so the description must compensate, and it does: both distrito and especialidad get example values and pointers to the enumerating tool (listar_filtros categoria='distritos'/'especialidades'). This fully disambiguates the two required params.

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 (Lista) and resource (órganos jurisdiccionales/salas) scoped by distrito and especialidad (corte superior). It clearly distinguishes itself from siblings like listar_filtros by explaining that this returns the sala catalog rather than the filter catalog it consumes.

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?

Gives clear context for use: pass the returned EXACT 'nombre' (or 'codigo') as the 'sala' filter in downstream tools, and points to listar_filtros for valid distrito/especialidad values. It does not, however, state explicit when-not-to-use conditions versus alternatives.

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