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

With no annotations, the description carries the transparency burden. It discloses that the tool searches across multiple categories at once, which is a behavioral trait, but it does not explain how results are returned, limit handling, or any other nuances. This is minimal but not misleading.

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, well-structured sentence that starts with the key concept 'Metabuscador' and lists the search scope. Every word adds value, and there is no redundancy or filler.

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 output schema, annotations, and parameter descriptions, the description should provide more context about result structure or how the limit applies. It covers the basic purpose and scope but leaves significant gaps for an agent trying to predict the tool's behavior.

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 compensate. It indirectly indicates 'un texto' corresponds to the query parameter, but it completely omits any explanation of 'limite_por_tipo'. With two parameters and one unaddressed, it fails to adequately clarify the tool's inputs.

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 is a 'Metabuscador' that searches a text simultaneously across professionals, entities, projects, events, interviews, and news. This specific verb and resource list effectively distinguishes it from the sibling tools that target individual categories.

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 word 'simultáneamente' implies this tool is for cross-category searches, but there is no explicit guidance on when to prefer it over the individual buscar_* tools or any exclusions. The context of sibling tools makes the use case apparent, but the description does not articulate it directly.

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