ebay_create_shipping_fulfillment

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It states the required scope but does not mention side effects (e.g., updating order status, sending notifications), idempotency, or error conditions. It fails to convey whether it is destructive or reversible.

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 extremely concise with two sentences: the first states purpose, the second states required scope. It is front-loaded and contains no filler. Every word earns its place.

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?

Despite having a nested object parameter and no output schema, the description offers no details on return values, success confirmation, error handling, or validation rules. A mutation tool of this complexity should provide more context.

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 100% with minimal descriptions ('The order ID', 'Shipping fulfillment details including tracking number'). The description adds no additional parameter context beyond the schema. Baseline 3 is appropriate as schema does the heavy lifting.

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 the action ('Create') and the resource ('a shipping fulfillment for an order'). This verb+resource combination distinguishes it from sibling tools like ebay_get_shipping_fulfillment (read) and ebay_update_* tools.

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?

The description only mentions required OAuth scope but provides no guidance on when to use this tool versus alternatives. It does not specify prerequisites (e.g., order must be paid), when not to use it, or conditions for success. With many sibling tools, explicit usage guidance is missing.

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