buscar_instructivos

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

With no annotations, the description carries the full burden. It discloses that the tool returns fragments and official URLs ("Devuelve fragmentos y URLs oficiales") and warns against inventing requirements outside those fragments ("no inventar requisitos fuera de los fragmentos"). This provides useful behavioral context, though it lacks details on authentication, rate limits, or error 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 description is three concise sentences, front-loaded with the main action, then usage, then output and caution. Every sentence adds value with no redundancy.

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?

Despite having no output schema or annotations, the description provides the essential context: what it searches, when to use it, what it returns, and a safety warning. For a simple one-parameter search tool, this is nearly complete, but it could mention pagination or result limits.

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 schema has 0% description coverage for the single parameter 'consulta'. The description implies the parameter is the search query by mentioning topics to search for, but it never explicitly defines 'consulta' or gives format examples. This is adequate compensation but not outstanding.

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 identifies the tool as searching an official documentary index sourced from public pages/PDFs ("Buscar en índice documental oficial"). The verb 'buscar' plus specific resource distinguishes it from sibling tools like buscar_noticias or buscar_web_oficial, which target different content types.

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 provides explicit use cases: "Usar para requisitos, documentación, obras, licencias, tasas y trámites." This gives clear context for when to use the tool, though it does not mention alternative tools or exclusion scenarios, so it falls short of a 5.

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