buscar_fuentes

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions the function and implies URLs are returned, but omits any details about read-only status, output format, pagination, or limitations. This is a significant gap for a search tool with no annotation support.

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 sentence that efficiently conveys both purpose and usage. It is front-loaded and contains no redundant information, earning a perfect score.

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 covers the core purpose and a usage condition, but lacks details about the return format, result count, or any prerequisites. Given the absence of an output schema and annotations, more information is needed for full contextual completeness, though the tool's simplicity keeps it at a minimum viable level.

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%, and the description merely repeats the parameter names ('consulta/categoría') without explaining their meanings, expected values, or how they interact. It does not help an agent construct correct inputs beyond the schema's basic type declarations.

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 searches official public sources by query/category, using a specific verb and resource. It also mentions the use case of citing exact URLs, which distinguishes it from sibling tools like 'buscar_noticias' or 'buscar_web_oficial'.

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 says 'Usar antes de contestar si necesitás citar URLs exactas', providing a clear condition for use. It does not name alternative tools, but the context is sufficient for an agent to decide when to invoke it.

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