ebay_get_sales_taxes

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

The readOnlyHint annotation already signals a safe read operation, and the description's 'Get all' phrasing is consistent with that. The description adds mild value by indicating the result covers the full set of sales tax tables for a country, but it does not disclose response format, pagination, or any other behavioral details beyond what annotations imply.

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, efficient sentence with no redundant words. It front-loads the action and clearly states the object and scope.

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?

For a read-only tool with a single, well-documented parameter, the description is almost sufficient. The absence of an output schema means the agent is not told what the response looks like, but the low complexity and readOnlyHint keep this from being a major gap.

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%, and the schema already fully documents 'countryCode' as a required ISO 3166-1 code. The description only restates the country-level scope and adds no additional semantic or format details.

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 states a clear verb ('Get'), resource ('sales tax tables'), and scope ('for a country'). It communicates that this is the plural/bulk retrieval operation, but it does not explicitly differentiate itself from similar siblings like 'ebay_get_sales_tax' or 'ebay_get_sales_tax_jurisdictions'.

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?

There is no guidance on when to use this tool versus alternatives such as 'ebay_get_sales_tax' or 'ebay_create_or_replace_sales_tax'. The description only states what the tool does, with no context about when it is the appropriate choice.

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