Consultar un producto

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description does not need to restate those. It adds a little context by specifying the breadth of the returned data, but it does not disclose behavior beyond what the annotations and the stated return scope already imply, such as pagination, errors, or availability constraints.

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, front-loaded sentence that directly states the action and the object. Every word carries meaning, and there is no redundant or filler content.

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 output schema and annotations cover return values and safety profile, and the single required parameter is simple. However, the description does not clarify how to obtain or interpret product_id, nor does it situate the tool relative to its siblings, leaving minor but real gaps for autonomous selection and invocation.

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 would need to compensate by explaining product_id semantics. It does not clarify the format, source, or scope of product_id beyond the schema's type/length constraints and the property name, leaving some ambiguity for an agent.

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 specific verb ('Devuelve') and identifies the resource ('un producto') while enumerating the exact data returned: variants, sellers, offers, and images. This clearly distinguishes the tool from siblings like get_product_image (single image) and search_products (search/browse).

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 gives no explicit guidance about when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. Sibling tools such as search_products and get_product_image are not referenced, leaving the agent to infer usage from the resource scope.

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