tiendanube_update_product

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

With no annotations, the description adds the behavioral detail that only provided fields are updated (partial update). However, it lacks information on side effects, permissions, rate limits, or destructive potential, which is expected for an update tool.

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?

Two sentences with no redundant information. The description is front-loaded with the core action and includes the essential behavioral note about optional fields, making it highly concise.

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?

Despite 26 parameters and no output schema, the description is minimal. It does not explain what the tool returns, validation rules, or how to use complex fields like tags or categories. The lack of output schema description further reduces completeness.

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 coverage is 100% with detailed parameter descriptions. The description does not add additional meaning beyond the schema, maintaining the baseline score. The statement 'All fields are optional except product_id' is already implied by the required field.

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 'Update an existing product,' which is a specific verb and resource. It distinguishes from sibling tools like create, get, or update for other entities. It also clarifies that only provided fields are updated, adding specificity.

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?

No explicit guidance on when to use this tool versus alternatives like tiendanube_update_product_variant or tiendanube_update_category. The description does not provide context for choosing this tool over siblings, leaving the agent without comparative information.

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