Update Item

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

The description discloses patch semantics: omitted fields stay unchanged, explicit nulls/empty arrays overwrite. This adds behavioral context beyond annotations which only indicate non-readOnly and non-destructive. The description covers key behaviors adequately.

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, first stating purpose, second explaining behavior. No filler or repetition. Extremely efficient and front-loaded.

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 complexity with nested objects and patch semantics, the description covers essential behaviors. No output schema exists, so return values are not expected. It is complete enough for a tool with high schema coverage and clear sibling 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 coverage is 100%, providing detailed descriptions for all parameters. The description adds value by explaining the overall patch behavior (nulls/empty arrays overwrite), which is not in the schema. This enriches parameter understanding beyond the schema alone.

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 updates selected fields of an item by ID, specifying the verb 'update' and the resource 'item by id'. It distinguishes from reconstructing the full item, and the existence of sibling create/delete tools further clarifies its purpose.

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 explicitly advises 'Use this for partial edits instead of reconstructing the full item', providing clear when-to-use guidance. It does not explicitly state when not to use or offer alternatives, but the context is sufficient for an agent.

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