buscar_producto

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

With no annotations provided, the description carries the behavioral burden and does add some return context: price and stock by warehouse. However, it does not describe search semantics (partial vs exact matching, ordering), error behavior, or pagination beyond what the schema already states. 'En voseo' is an unusual note that is not clearly explained.

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 only two short sentences and is front-loaded with the core action. The trailing 'en voseo' is odd and slightly confusing, keeping it from 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 tool is simple with two fully documented parameters and no output schema, so the description's note about returning price and stock by warehouse is useful. Still, it omits the critical sibling differentiation and search behavior details that an agent would need to choose it over precio_producto or stock_producto.

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 100%, so both q and limit are already documented. The description's 'por nombre' aligns with q but adds no syntax, matching rules, or defaults beyond the schema. Baseline 3 is appropriate.

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 states a specific verb and resource: 'Busca productos por nombre' (search products by name). It is clear what the tool does, but it does not distinguish itself from siblings like precio_producto or stock_producto, which also relate to prices and stock per warehouse.

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 search tool versus precio_producto or stock_producto. The description does not mention exclusions, prerequisites, or the fact that it is a name-based search returning multi-warehouse data.

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