set_customer_property_values

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

With no annotations provided, this description carries the full burden and does well, disclosing that values are replaced, only specified properties change, and outlining the value format for each property type. It lacks details on permissions or error behavior but is substantially transparent.

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 well-structured with a clear opening sentence, followed by behavioral notes and an args section. It is slightly long but every sentence earns its place, providing necessary detail without redundancy.

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 description covers the main complexities of this tool, including partial updates, value type coercion, and array handling for non-multi properties. It is complete for a setter tool, though it omits details about response behavior or edge cases like empty lists, but overall it is sufficient given its complexity.

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?

The description adds extensive meaning beyond the bare schema by explaining customer_id as a UUID and detailing the values mapping structure with examples. It also provides per-type value formats and the single-item list rule, which are essential for correct invocation.

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 the tool's function: 'Set a customer's custom property values, replacing any current ones.' It identifies the specific resource (customer's custom property values) and differentiates from sibling tools like set_work_item_property_value and get_customer_property_values.

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 provides clear context by explaining that 'Only the properties named are touched; the rest keep their values,' which guides the user on partial updates. It does not explicitly name alternatives but implies when to use this tool versus others, covering the main usage scenario.

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