Update Item

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

Annotations indicate a non-destructive write. The description adds crucial behavioral details: omitted fields stay unchanged while explicit nulls and empty arrays overwrite stored values. This goes beyond annotations and helps the agent understand the patch semantics.

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?

Three sentences: first states purpose, second explains patch behavior, third gives usage guidance. No unnecessary words, highly structured and efficient.

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 tool has 2 required parameters with nested objects. The description covers the critical patch merging semantics and usage context. No output schema exists, but the behavior is sufficiently documented. Complete for the complexity level.

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%, so baseline is 3. The description adds value by explaining the patch behavior (null/empty overwrite) which is not in the schema descriptions. This enhances understanding of the patch parameter.

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 verb 'update', resource 'item by id', and specifies 'selected fields' indicating partial update. It distinguishes from sibling tools by emphasizing partial edits instead of full reconstruction.

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

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