update_marketplace_price

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

With no annotations, the description must disclose behavioral traits. It reveals that confirm=True is needed, which suggests a confirmation step. However, it does not mention that the operation is destructive (price overwrite), any authorization requirements, rate limits, or response behavior. This is adequate but leaves gaps.

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 very short (two sentences) and front-loaded with the purpose. It wastes no words but could benefit from being slightly more structured or expanded to cover key parameters.

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 tool's mutating nature, the description omits crucial context: supported marketplaces, price format, whether the update is immediate, and how errors are handled. The presence of an output schema reduces the need to explain return values, but the overall description is insufficient for safe and correct usage.

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 only adds value for the 'confirm' parameter by stating it must be true. The other parameters (sku, price, marketplace, product_type) receive no explanation beyond their names. This barely improves understanding.

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 'Cambiar precio en un marketplace' clearly states the action (change price) and resource (marketplace). It distinguishes the tool from sibling tools like 'bulk_update_prices' only implicitly, but the name itself is specific. The mention of 'Requiere confirm=True' adds a key detail.

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 only notes that confirm=True is required, implying it must be set for the action to execute. It provides no guidance on when to use this tool versus alternatives (e.g., bulk_update_prices, sync_marketplace_prices), nor does it specify prerequisites or context.

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