set_sealed_inventory

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

Describes operation as a 'real write' with 'upsert' semantics, indicating mutation. However, no annotations exist, and the description could mention more about side effects (e.g., overriding previous quantity is implied but not explicit). Still, it provides adequate transparency for a simple write tool.

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, each purposeful: operation description, sibling alternative, requirements. No unnecessary words. Front-loaded with primary action.

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?

For a simple write operation with no output schema, the description covers purpose, parameters, behavior, and prerequisites. No relevant missing context identified.

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 covers both parameters 100%, but description adds value: explains where to get sealedProductUuid (from get_sealed_products or get_sealed_product) and clarifies that quantity is absolute (not delta). This helps the agent understand parameter semantics beyond schema.

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?

Clearly states the tool adds or updates a sealed product in the user's inventory by setting absolute quantity (upsert). Distinguishes from sibling remove_sealed_inventory by name. Verb+resource+operation are explicit.

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 mentions when to use alternative (remove_sealed_inventory for deletion). Also states it's Premium-gated and requires IWMM_API_KEY, providing clear usage conditions.

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