ebay_create_consign_preference

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

No annotations are provided, so the description carries full burden. It only states the action (create) without disclosing behavioral traits like authentication requirements, side effects, idempotency, or potential errors. The schema has an open object parameter, so the description adds no context about allowed properties.

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 that efficiently conveys the core purpose. It is front-loaded with the action. However, it is arguably too brief given the missing details about the parameter and usage, which slightly reduces its practical value.

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 complexity (one unstructured object parameter, no output schema), the description is incomplete. It does not explain what a consign preference entails, what properties the nested object should contain, or what the return value is. Essential context for an agent to use the tool correctly is missing.

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% (one parameter), but the schema's description ('Consign preference data') is minimal. The tool description adds no additional meaning or constraints, so it does not improve upon the schema. Baseline 3 is appropriate as it neither harms nor significantly helps.

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 (consign preference for international shipping). It distinguishes itself from other eBay create tools by specifying the domain of international shipping consign preferences, which is unique among siblings.

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 is provided on when to use this tool versus alternatives (e.g., when to use create_consign_preference vs create_shipping_fulfillment or other preference tools). There is no mention of prerequisites or conditions.

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