ebay_create_consign_preference

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

The description indicates mutation ('Create') but provides no details on side effects, permissions, idempotency, or constraints. Without annotations, this is insufficient for safe usage.

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, which is concise but omits necessary context. It earns its place but does not fully inform the agent.

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 lack of output schema and annotations, and only one loosely defined input parameter, the description is incomplete. It does not explain return values, request structure, or usage 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?

Although schema coverage is 100%, the parameter description ('Consign preference data') adds no meaningful information beyond the schema. The parameter is a loosely typed object with additionalProperties, so the description should explain what properties are expected.

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') with a specific context ('for international shipping'). This differentiates it from sibling tools like 'ebay_get_consign_preferences'. However, it does not explain what a consign preference is.

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 versus alternatives. The description does not mention prerequisites, when not to use, or related tools (e.g., 'ebay_get_consign_preferences' for retrieval).

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