buscar_por_resolucion

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

No annotations are provided, so the description carries the full burden. It only states that it searches, without disclosing whether it returns a list, if matching is exact or partial, or any limitations or side effects. The example hints at accepted formats but doesn't describe output or error behavior. This is insufficient for a no-annotation context.

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, concise sentence with a clear example. It wastes no words and is front-loaded with the action verb.

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 simple tool with 2 well-described parameters and no output schema, the description covers the input but omits return values and usage context relative to siblings. This leaves the agent uncertain about what to expect, though the low complexity mitigates the gap. The description is adequate but not complete.

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 already describes both parameters with examples and 100% coverage. The tool description's example (Resolución 0601/2026-S2) reinforces the format but doesn't add meaningful new semantics beyond the schema. Thus, baseline 3 applies.

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 resolutions by number and year, using a specific verb ('Busca') and resource ('resoluciones'). It distinguishes from siblings like buscar_por_nombre (which searches by name) and buscar_en_resolucion (which searches within a resolution).

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 the use case: when you have a resolution number and year, but does not explicitly compare with alternatives like buscar_por_nombre or buscar_en_resolucion. No exclusions or conditions are provided, leaving the agent to infer from the tool name. The example format helps but isn't explicit guidance.

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