emu_patch_inventory_item

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

No annotations are provided, so the description must disclose behaviors such as whether it performs a partial merge, overwrites fields, or validates the body against schema. It does none of this. The agent has no information about error behavior, idempotency, or side effects, making it fully opaque.

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?

The description is a single short sentence, but it is under-specified rather than efficiently concise. It does not front-load critical information; it simply restates the operation name in a slightly expanded form. Every word is present but the sentence fails to convey meaningful guidance.

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?

This is a complex tool with 3 required parameters, a large enum, and a free-form body object, yet no output schema and no behavioral context. The description provides none of the essential details an agent needs to call it correctly, such as supported resources, body format, or expected outcomes.

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 0%, and the description does not compensate. It does not explain the meaning of 'resource' (beyond the enum), 'id', or 'body', nor the structure of the patch payload. The agent is left without any semantic guidance for constructing a correct request.

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 the action 'Patch' and the object 'v2 inventory object', which is a specific verb+resource pair. However, it does not clarify what 'v2' means or differentiate this from sibling operations like emu_upsert_inventory or emu_delete_inventory_item beyond the verb. It is clear enough to identify the intent but lacks specificity about the resource types it applies to.

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?

There is no guidance on when to use this tool versus alternatives. With siblings like emu_upsert_inventory (for create/update) and emu_delete_inventory_item, the description gives no context about partial updates, required state, or scenarios favoring patch over upsert. This leaves the agent to guess the appropriate selection.

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