ebay_update_rate_table_shipping_cost

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

Annotations declare readOnlyHint=false and idempotentHint=true, so the safety profile is covered. The description adds real context beyond the annotations: success is a 204 No Content response (no body), the supported marketplaces, and the required OAuth scope.

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 action and target, then layers provenance, response, marketplaces and scope. Dense but every clause earns its place; no filler or repetition.

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?

Covers the mutation's outcome (204), the scope needed, marketplace support, and where to source the IDs. With 100% schema coverage, annotations present, and no output schema to explain, this is complete for correct invocation.

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 the schema already documents both params and the nested rate fields. The description adds provenance for the two IDs (which sibling tools supply them), which is useful but marginal over the fully-documented schema.

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 (Update) plus the exact resources mutated (shippingCost and/or additionalCost for rates in a shipping rate table). It also names the underlying eBay API operation, so the agent can distinguish this from the many other shipping-related siblings.

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?

Provides clear prerequisites and routing: rateTableId comes from ebay_get_rate_tables, each rateId from ebay_get_rate_table, and the operation requires the sell.account scope. It stops short of an explicit when-to-use/when-not statement, but for this narrow mutation there is no competing sibling to steer away from.

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