ebay_create_consign_preference

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It only says 'Create' which implies mutation, but provides no details on idempotency, overwrite behavior, side effects, or required permissions. This is a significant gap for a creation 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?

The description is a single sentence, which is concise but lacks structure. It could benefit from additional sentences or bullet points to cover parameter details and behavioral context while remaining concise. Currently, it under-specifies.

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 of a creation tool with a freeform body and no output schema or annotations, the description is severely incomplete. It does not explain return values, error conditions, prerequisites, or how to interact with related tools like ebay_get_consign_preferences. The agent cannot reliably use this tool based solely on this description.

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?

The input schema has one parameter 'body' which is a freeform object with no defined properties (schema description coverage 0%). The description adds no meaning about what fields the body should contain, how to structure it, or any constraints. This leaves the agent completely uninformed about how to populate the parameter.

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 is specific enough to distinguish from siblings like ebay_get_consign_preferences. However, it does not explain what a consign preference is, which would be helpful for complete clarity.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any prerequisites or conditions. The agent is left to infer context from the sibling list.

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