ebay_create_or_replace_sales_tax

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

With no annotations, the description must convey behavioral traits. It says 'Create or replace' but doesn't explain what 'replace' entails (e.g., full overwrite, merge). No mention of idempotency, side effects, or unusual schema features like additionalProperties: true on salesTaxBase.

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 short sentence, which is concise but omits important details like parameter context and behavioral implications. It is front-loaded with the action, yet under-specified.

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 params, a nested object, and no output schema or annotations, the description is insufficient. It does not explain what the tool returns, that the jurisdiction must exist, or how the sales tax table is applied.

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 coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema. The nested salesTaxBase object has gaps (e.g., no description for salesTaxPercentage format), but the description does not compensate.

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), resource (sales tax table), and scope (for a jurisdiction). It distinguishes from sibling tools like ebay_delete_sales_tax and ebay_get_sales_taxes.

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 vs alternatives such as ebay_bulk_create_or_replace_sales_tax or ebay_get_sales_taxes. Prerequisites like needing a valid jurisdictionId are not mentioned.

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