Update Item

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

Annotations already show non-read-only, non-destructive. The description adds crucial details about patch semantics (nulls overwrite, omitted fields unchanged), enhancing transparency beyond annotations.

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 states purpose, second explains patch behavior. Efficient, front-loaded, with no wasted words.

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?

Covers update semantics, null handling, and partial edit guidance. No output schema needed; tool is mutation-focused. Could mention error specifics but not critical given schema coverage.

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 has 100% description coverage, so baseline is 3. The description adds behavioral context about how the patch object is applied, justifying a 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 states 'Update selected fields of an item by id' with specific verb and resource. It clarifies partial vs full updates, distinguishing from sibling creation/deletion tools.

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 recommends using for partial edits rather than full reconstruction, providing clear usage context. It implies when not to use but does not list specific alternative tools.

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