consultar_documentos_locales

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

No annotations are provided, so the description must carry the burden. It discloses it searches and reads documents (read-only behavior), but does not mention authentication needs, rate limits, or limitations on file size/encoding. Adequate but minimal.

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 that conveys the main purpose, supported formats, and scope. No wasted words.

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 lacks details on the return structure (e.g., whether it returns snippets or full paragraphs, how matches are presented). With no output schema, this is a gap. Also, no error handling info. But given the tool's simplicity, it is minimally acceptable.

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%, baseline 3. The description adds value by clarifying that omitting 'query' lists available documents. For 'max_caracteres', it restates the schema description but adds 'de cada coincidencia' for context.

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 it searches and reads information from local manuals, regulations, and guides in the docs/ folder, supporting .pdf, .txt, .md formats. It distinguishes from sibling tools like 'descargar_y_leer_documento' which likely handles external documents.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies local document search, but does not exclude cases where another tool might be better.

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