buscar_articulos

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

No annotations are provided, so the description must cover behavioral traits. It discloses a hybrid semantic+FTS search, that returned text is literal with provenance. However, it does not mention side effects, read-only nature, rate limits, or what happens on no results—leaving gaps for an agent.

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-loading the core purpose and usage context. Every sentence adds value—scope, search type, use case, and output nature—without extraneous detail.

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 adequate purpose and usage guidance, the description is incomplete given the complexity. No output schema exists, parameters are unexplained, and behavioral details like query syntax or pagination are missing. The description leaves significant gaps for an AI agent to invoke correctly.

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 explain parameters. It only implicitly covers the 'query' parameter by referencing search intent. The 'limit' and 'tipo_norma' parameters are entirely unexplained, leaving the agent without guidance on how to use or default behaviors.

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 the tool performs a deep hybrid search over 1.2 million current articles, specifying it is for when the user needs to find which regulation governs a topic but doesn't know where to look. This distinguishes it from sibling tools like buscar_normas (search norms by name) and leer_articulos (read articles).

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 explicitly tells when to use this tool: 'Para "que norma regula X" cuando no sabes donde mirar.' This provides clear guidance for use cases where the user is unsure of the specific norm, making it distinct from searching by known criteria.

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