ebay_create_inventory_item

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

No annotations exist, so the description must cover behavior. It mentions OAuth scope but fails to disclose important traits like idempotency (create vs. replace implications), required permissions beyond scope, rate limits, or side effects (e.g., overwritten data).

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 short (two sentences) but not information-dense. One sentence is dedicated to OAuth scope, which could be in the annotation. It is concise but lacks substantive 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?

Given the complex nested schema (e.g., product, availability, packageWeightAndSize) and no output schema, the description is insufficient. It does not explain return values, error scenarios, or the behavior on replace. More context is needed for effective tool usage.

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?

Input schema covers 100% of parameters with descriptions ('The seller-defined SKU' and 'Inventory item details'). The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states 'Create or replace an inventory item,' specifying the verb and resource. It is straightforward but does not differentiate from sibling tools like ebay_bulk_create_or_replace_inventory_item.

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?

No guidance on when to use this tool vs alternatives (e.g., bulk vs single item). No context on prerequisites, expected outcomes, or scenarios. Only OAuth scopes are provided, which are not usage guidelines.

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