ebay_get_rate_table

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely useful context beyond that: the returned fields, the supported marketplaces, and the required OAuth scopes (sell.account or sell.account.readonly). It stops short of describing anything about pagination or error behavior, but for a single-item read this is strong.

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?

Front-loaded with the core action, then the ID provenance, downstream usage, region constraints and scopes. Every sentence earns its place, though the parenthetical API citation is slightly redundant with the purpose statement.

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?

No output schema exists, so the description correctly carries the return-shape burden by naming the returned fields. Combined with the auth scope, region coverage, ID source and downstream sibling, an agent has everything needed to select and invoke it correctly.

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% for the single rateTableId parameter, so the baseline is 3. The description adds provenance for the ID (call ebay_get_rate_tables), though the schema also states this (attributing it to v1 getRateTables), so the marginal gain is modest rather than decisive.

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?

States a specific verb and resource ('Get one shipping rate table') and enumerates exactly what it returns (rates, rateIds, regions, shipping costs). It also names the sibling used to obtain the ID and the sibling that consumes the rateIds, so it is clearly distinguishable from ebay_get_rate_tables and ebay_update_rate_table_shipping_cost.

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?

Explicitly says where the required rateTableId comes from ('from ebay_get_rate_tables') and how the result is consumed ('use the rateIds with ebay_update_rate_table_shipping_cost'), establishing both the input path and downstream workflow. Region support (US, CA, GB, DE, AU, FR, IT, ES) further narrows when this tool is applicable.

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