ebay_create_or_replace_sku_location_mapping

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

With no annotations, the description must disclose behavioral traits. It states 'create or replace' implying idempotent behavior, but does not clarify what happens if the mapping already exists (replaces? errors?). It also omits side effects, idempotency guarantees, or error conditions.

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 concise, consisting of two sentences. The first sentence clearly states the action. The second sentence provides required OAuth scope, which is useful but not strictly necessary in the description. No fluff, but could be structured to front-load key behavioral info.

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 tool has 3 required parameters, no output schema, and no annotations, the description is incomplete. It does not explain what the 'body' parameter should contain, what the response looks like, or any prerequisites. Sibling tools exist but aren't referenced.

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%, so each parameter has a brief description in the schema. The tool description adds no additional parameter meaning beyond what the schema provides, so a baseline of 3 is appropriate. The body parameter description is vague but covered.

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 or replace' and the resource 'SKU location mapping for a listing'. It explains the purpose of mapping a SKU to fulfillment center locations. It distinguishes itself from sibling tools like ebay_get_sku_location_mapping and ebay_delete_sku_location_mapping by focusing on creation/replacement.

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 mentions required OAuth scopes but provides no guidance on when to use this tool versus alternatives like ebay_get_sku_location_mapping or ebay_delete_sku_location_mapping. It does not specify prerequisites or conditions for creating vs. replacing a mapping.

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