emu_upsert_inventory

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'Create or upsert,' which implies a mutation but does not explain upsert semantics (e.g., whether it replaces, merges, or fails on conflict) or any side effects. There is no mention of authentication, rate limits, or response behavior. This is minimal disclosure.

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 sentence and not wordy, but it is under-specified. It is front-loaded with the action but lacks the necessary details to be useful. Every sentence should earn its place; this sentence is short but does not convey enough information, so it does not justify its brevity.

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 tool complexity (2 required params, one with a large enum, no output schema) and the crowded sibling set, the description is severely incomplete. An agent cannot correctly call this tool without additional information about what 'v2 inventory object' means, how to structure the body, and how resource values affect behavior. The absence of annotations and output schema makes this description inadequate.

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%, so the description must compensate for the lack of parameter documentation. However, the description does not mention either parameter (resource or body) or how they relate to the 'inventory object.' It adds no meaning beyond the bare schema, leaving the agent without guidance on what the body should contain or how resource values map to inventory types.

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 a specific verb ('Create or upsert') and a resource ('a v2 inventory object'), which indicates the core action. It is distinct from sibling tools like list/get/delete/patch inventory items, though it doesn't explicitly name those alternatives. The term 'v2 inventory object' is somewhat vague without additional context, but the purpose is generally clear.

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 the many inventory-related siblings (e.g., emu_patch_inventory_item, emu_seed_fixtures). No context is provided about prerequisites, idempotency, or typical scenarios. The description gives no direction on choosing this tool over alternatives.

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