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 carries the full burden. It only states 'create or replace', which implies overwriting behavior, but fails to disclose any other behavioral traits such as idempotency, limits, or side effects. No details about what happens when a tax table already exists or error conditions are given.

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 extremely concise at 4 words, which is efficient but omits critical information. Every sentence should earn its place, and here the conciseness comes at the expense of completeness, making it minimally adequate.

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 lack of annotations and output schema, the description should provide more context about input format, limits, and behavior. It only specifies bulk operation, but the nested structure of 'requests' is not explained. The description is insufficient for an agent to correctly invoke the tool without examining the schema deeply.

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 single parameter 'requests' has a schema description 'Array of sales tax requests', which provides basic context. However, the tool description adds no extra meaning beyond the schema. Since schema description coverage is 100%, the baseline of 3 is appropriate.

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 (create/replace), resource (sales tax tables), and the bulk aspect distinguishes it from the singular sibling ebay_create_or_replace_sales_tax. It provides a specific verb and resource, effectively differentiating from related tools.

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 given on when to use this tool versus alternatives. The word 'bulk' implies multiple operations, but there is no explicit statement about batch usage, prerequisites, or exclusion of singular use. The sibling ebay_create_or_replace_sales_tax exists for single operations, but the description does not mention it.

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