ebay_get_sales_tax

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

The readOnlyHint annotation already communicates that this is a safe read operation, and the description merely repeats that idea with 'Get'. It adds no additional behavioral context such as required prerequisites, return format, or relationship to jurisdiction discovery.

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 filler. It is front-loaded with the core action and resource, though the phrase 'sales tax table' could be more precise about the returned data.

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 two-parameter read-only getter with fully documented parameters, the description is minimally viable. However, it does not clarify what the sales tax table contains, how jurisdictionId is obtained, or how this relates to sibling tools like ebay_get_sales_tax_jurisdictions.

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%, so both parameters are already documented ('Two-letter ISO 3166 country code' and 'Tax jurisdiction ID'). The description adds only the word 'jurisdiction' and does not provide meaningful detail beyond the schema, so baseline 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 uses a specific verb ('Get') and names the resource ('sales tax table') scoped to a jurisdiction. It is clear what the tool does, though it does not explicitly distinguish itself from siblings like ebay_get_sales_taxes 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?

The description gives no guidance on when to use this tool versus alternatives. Given close siblings like ebay_get_sales_taxes and ebay_get_sales_tax_jurisdictions, an agent is not told which tool fits which scenario or whether jurisdiction IDs must first be obtained from another call.

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