buscar_entidades

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

No annotations are provided, so the description carries the full burden. It usefully discloses the session model ('GLOBAL y compartida entre tools; si se omite se abre una temporal') and the exact return shape, but says nothing about it being a read-only network call, error behaviour, or rate limits.

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 labelled Args and Devuelve sections; each parameter line earns its place. Slightly verbose in the ses parenthetical but overall efficient.

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 no output schema, the description supplies the return contract ('ok', 'ses', 'total', 'filas': [{index, ruc, tipo_documento, nombre}]) and how to consume it downstream, so an agent has everything needed to call and chain this 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?

Schema coverage is 0%, so the description must compensate, and it documents all four parameters: nombre with an example ('SEDAPAL'), ruc as an exact 11-digit value, sigla, and ses as an optional shared previous session. It adds real meaning over the bare schema, though it does not clarify matching semantics (partial vs exact) for nombre/sigla.

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 (Busca) and resource (ENTIDADES del Estado peruano) plus the search axis (nombre, RUC o sigla) and the source (buscador SEACE). It clearly distinguishes itself from data tools like buscar_ocos/buscar_procesos by being the entry point that yields the RUC those siblings consume.

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?

Explicitly routes downstream: 'Usa el ruc para buscar_ocos y el nombre exacto para buscar_procesos(entidad=...)', which tells the agent how this fits the workflow. It stops short of stating when-not to use it (e.g. when you already know the entidad), so it is clear context without exclusions.

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