ebay_bulk_create_or_replace_sales_tax

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

No annotations are provided. The description only states the action but does not disclose behavioral traits such as idempotency (create vs replace logic), whether it overwrites existing tables, rate limits, or required auth scopes. Minimal value beyond the tool name.

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 very concise (one sentence, 7 words). It efficiently conveys the core action. However, it is so brief that it sacrifices completeness. It earns its place but could be slightly more informative without losing conciseness.

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 schema with required fields, no output schema, no annotations), the description is incomplete. It does not explain the structure of 'requests', what constitutes a valid sales tax table, or the behavior on replace. Additional context about jurisdictions, country codes, or typical usage is missing.

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 'requests' with a schema description 'Array of sales tax requests'. The description does not add any meaning beyond the schema. Nested fields (countryCode, jurisdictionId, salesTaxBase) lack descriptions, but since schema coverage is considered 100% for the top level, baseline is 3. No additional value added.

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: 'Bulk create or replace sales tax tables'. It uses specific verbs (create, replace) and a resource (sales tax tables). The presence of sibling tools like 'ebay_create_or_replace_sales_tax' (non-bulk) and 'ebay_delete_sales_tax' shows that this tool is differentiated by the bulk operation.

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 versus alternatives. There is a non-bulk version ('ebay_create_or_replace_sales_tax') and other sales tax tools, but the description does not explain when bulk is appropriate, prerequisites, or any context for choosing this tool.

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