ebay_create_address_preference

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

With no annotations, the description carries full burden but only says 'Create'. It fails to disclose behavioral traits such as idempotency, error handling, limits, or what happens if the address preference already exists. The mutation nature is implied but not elaborated.

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 with no wasted words, achieving conciseness. However, it is almost too brief, lacking depth that could improve utility. It is front-loaded with the key action.

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 (nested object parameter, no output schema, no annotations), the description is highly incomplete. It does not explain the required structure of addressPreference, typical fields, return value, or error conditions. A creation tool requires more detail to be usable.

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 schema describes the single parameter as 'Address preference data' with additionalProperties: {}, which is vague. The description adds context 'for international shipping', clarifying the purpose of the parameter. However, it does not explain the structure or constraints of the addressPreference object, so it only partially compensates for the schema's lack of detail.

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 verb 'Create', the resource 'address preference', and the scope 'for international shipping'. It distinguishes from sibling tools like ebay_get_address_preferences (get vs create) and ebay_create_consign_preference (different preference type).

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 provides no guidance on when to use this tool, what prerequisites exist, or when alternatives might be preferred. It does not reference sibling tools or specify use cases versus alternatives like ebay_get_address_preferences.

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