update_offer_item

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

Discloses that updates use JSON Patch and require 'confirmed: true' to execute, but does not cover side effects, idempotency, error handling, or authorization beyond the access_token parameter.

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, no fluff, front-loaded with action and method, immediately followed by a key condition.

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 main purpose and a critical precondition, but missing details on return format, error scenarios, and proper usage of the patches array; no output schema to supplement.

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?

Adds meaning to 'patches' by mentioning JSON Patch and to 'confirmed' by stating it must be true, but does not explain 'offer_id' or 'access_token', and schema has no descriptions (0% coverage).

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?

Description clearly states verb (update), resource (offer item), and method (JSON Patch operations), distinguishing it from sibling tools like get_offer_item and list_offer_items.

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?

Implies use for updating offer items but lacks explicit guidance on when to use versus alternatives, such as comparing with get_offer_item for reading or create_* for new items.

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