buscar_web_oficial

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

It discloses that the tool is read-only and uses official URLs, which is useful since annotations are absent. However, it doesn't explain what happens if no adapter exists or describe any error/performance characteristics.

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 brief and front-loaded, conveying live search, adapter condition, and read-only nature in three short sentences. No redundant content.

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?

Given the lack of annotations and output schema, the description leaves gaps about expected results, error behavior, and the adapter concept. It's adequate for a simple tool but lacks full context.

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 input schema has one required parameter 'consulta' with 0% coverage in the description. The description doesn't add any extra meaning beyond the parameter name, which is self-explanatory as a search query.

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 performs live searches on official websites using adapters, which distinguishes it from sibling search tools like buscar_noticias or buscar_fuentes. The condition 'cuando existe adaptador' adds some ambiguity but doesn't obscure the core purpose.

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 implies usage when an adapter is available, but it doesn't provide explicit guidance on when to choose this tool over alternatives like buscar_fuentes or consulta_ciudadana. No exclusions or when-not cases are mentioned.

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