ebay_get_sales_tax

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

No annotations are present, so the description carries the full burden. It only says 'Get', which implies a read operation, but does not disclose permissions, rate limits, or whether the operation is read-only or potentially blocking. The behavior is superficially clear but lacks depth.

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 7-word sentence, perfectly concise with no extraneous information. Every word serves a purpose.

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 simple get operation with no output schema, the description is somewhat complete. It states the resource and scope, but does not describe the return value structure or potential error conditions. Given the sibling complexity, more detail about the output would be helpful.

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 100% description coverage with clear parameter descriptions. The description does not add extra meaning beyond 'countryCode' and 'jurisdictionId', so it meets the baseline 3 without enhancement.

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 'Get sales tax table for a jurisdiction' clearly states the action (get) and the resource (sales tax table) with context (for a jurisdiction). It is specific but does not differentiate from sibling tools like ebay_get_sales_taxes (plural) or ebay_get_sales_tax_jurisdictions, though the singular form implies a single jurisdiction.

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. Siblings include ebay_get_sales_taxes and ebay_get_sales_tax_jurisdictions, and no hints are given about which to choose based on the need for a single or multiple jurisdiction records.

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