Buscar doctrina jurídica chilena

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

No annotations are provided, so the description carries full disclosure burden. It mentions data sources and output fields but omits key behavioral traits: rate limits, whether PDFs are always available, authentication needs, or result sorting. Minimal insight into tool 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 a single short sentence, which is efficient. However, it could benefit from restructuring to separate core purpose from output details.

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?

No output schema is provided, so the description should clarify return structure. It mentions fields but does not specify ordering, pagination, or format details. With multiple sibling search tools, the description fails to disambiguate usage scenarios.

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 67% (limite and formato have descriptions, consulta lacks one). The tool description adds no additional meaning beyond the schema. It does not explain the consulta parameter or how to formulate queries effectively.

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 mentions data sources (OpenAlex, Crossref) and output fields (citas formales, DOI, abstract, PDF) but does not explicitly state the action (e.g., 'Search for legal doctrine'). The purpose is implied but not clearly defined, and it does not distinguish from sibling tools like obtener_doctrina or investigar_tema.

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 guidance on when to use this tool versus alternatives. It does not specify prerequisites, when not to use it, or provide any context for appropriate usage.

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