tiendanube_update_customer

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

No annotations provided, but description explains that only provided fields are updated and existing data is preserved. This is good disclosure of update behavior. Does not mention permissions or side effects, but sufficient.

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, front-loaded with purpose, followed by usage and behavior. No fluff, every word adds value.

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?

With 14 parameters and no output schema, the description is sufficient for an update operation. Lacks mention of return value or error conditions, but overall adequate given the context.

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 covers 100% of parameters with descriptions. The description adds that all fields except customer_id are optional and that only provided fields will be updated, which supplements the schema. Baseline 3 raised to 4.

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 it modifies existing customer information, lists categories of updatable fields (personal details, contact, notes), and uses the verb 'Modify' with resource 'customer'. It distinguishes from create_customer and other update tools for different entities.

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?

Explicitly states use cases: customer profile updates, data corrections, preference changes, maintaining records. Mentions partial update behavior. Could be improved by contrasting with create_customer, but still clear.

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