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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the patch semantics ('only the given fields change') and the null-to-clear convention for description, price and priority, which is a non-obvious mutation contract.

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 short sentences, zero filler; the core patch behavior is front-loaded and the null-clear rule follows as the only necessary exception detail.

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?

For a mutation tool with no output schema, the description covers the essential patch contract and clearing convention, while annotations cover idempotency and safety and the schema covers every parameter. Only error/permission behavior on invalid IDs is unaddressed, which is a minor gap.

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 100%, so the baseline is 3. The description goes beyond the schema by explaining the tri-state semantics of the nullable parameters (null clears the field), which the schema only hints at by listing null in the type union.

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?

States a specific verb and resource: 'Changes fields of one item.' The mention of 'one item' implicitly separates it from update_wishlist and the bulk add_items, but no sibling is named explicitly, so the agent must infer the routing.

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?

Usage is implied by the partial-update wording ('Only the given fields change'), which tells the agent this is the tool for modifying an existing item rather than creating one. However, there is no explicit when-to-use/when-not guidance or reference to the delete_item / reorder_items alternatives.

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