buscar_intenciones

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

No annotations are present, so the description carries the full burden of disclosing behavior. 'Busca' implies a read/search operation, but the description does not mention pagination behavior, result semantics, side effects, or any operational caveats.

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 with no filler, so it is concise. However, its terseness leaves important gaps in usage and parameter semantics, making it under-specified rather than effectively compact.

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?

An output schema exists, but the tool has six optional parameters and zero parameter documentation, and the description provides no usage context or clarification of domain-specific jargon. The definition is not complete enough for an agent to invoke the tool correctly in all cases.

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 none of the six parameters are described in the tool description. The description does nothing to compensate for the missing parameter documentation, leaving the agent to infer meanings from parameter names alone.

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 uses a concrete verb and resource: 'Busca intenciones de contratación', which distinguishes it from the sibling search tools by target resource. However, the parenthetical 'excepciones con difusión posterior' is cryptic and not explained, so the exact scope is not fully transparent.

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?

There is no guidance on when to use this tool instead of sibling search tools like buscar_procesos, buscar_proveedores, or buscar_convocantes. No contexts, exclusions, or alternative recommendations are given.

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