ebay_bulk_create_or_replace_sales_tax

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

With no annotations provided, the description must fully disclose behavioral traits. It only states 'create or replace' without explaining what 'replace' entails (e.g., overwrite or upsert), any side effects, or required permissions. The schema hints at structure but the description lacks essential context about the operation's behavior.

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, front-loaded sentence: 'Bulk create or replace sales tax tables'. It is concise, with no redundant words, and immediately conveys the tool's core function.

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 nested objects, one required parameter with a list, and no output schema or annotations, the description is insufficient. It does not explain the impact of 'replace', the structure of a sales tax table, or any required context like jurisdiction hierarchy. A more detailed description is needed for accurate tool invocation.

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 includes a description for the top-level 'requests' parameter ('Array of sales tax requests'), but inner fields like 'countryCode', 'jurisdictionId', and 'salesTaxBase' lack descriptions. The tool description adds no parameter insight beyond what the schema already provides, so it meets the baseline but does not improve understanding.

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 'Bulk create or replace sales tax tables' clearly states the action (bulk create or replace) and resource (sales tax tables). It effectively distinguishes from the sibling tool 'ebay_create_or_replace_sales_tax' by specifying 'Bulk', indicating it handles multiple jurisdictions at once.

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 is provided on when to use this tool versus alternatives such as the singular 'ebay_create_or_replace_sales_tax' or the retrieval tools. No context about prerequisites or exclusions is given.

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