ebay_create_flat_shipping_rules

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

Annotations only supply readOnlyHint=false, so the description carries real extra burden and meets it: it discloses the auth scope ('Requires sell.account'), the response shape ('204 No Content' = nothing returned), and the confirmation step. It stops short of stating idempotency or how it interacts with existing rules.

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 action is front-loaded in the first clause and the parenthetical API path and endpoint name are secondary. Dense but earns most of its length; minor redundancy from restating the endpoint name.

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 write tool with no output schema, the description covers purpose, scope requirement, return value and a follow-up read path, which is enough to call it correctly. It omits edge cases (overwrite/conflict behavior, rule validation limits).

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 marketplaceId (enum + header note) and the shippingRules subfields. The description's header mention ('X-EBAY-C-MARKETPLACE-ID') duplicates what the schema's marketplaceId description already states, so it adds little. Baseline 3.

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 ('Create flat-rate combined-shipping rules') and pins the API endpoint (Account API v2 createFlatShippingRules), which lets an agent distinguish it from close siblings like ebay_create_calculated_shipping_rules and ebay_create_promotional_shipping_rule without opening a schema.

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?

It gives a verification path ('confirm with ebay_get_combined_shipping_rules') and a scope requirement ('Requires sell.account'), but never states when to choose this over its near-identically named siblings (create_calculated_shipping_rules, create_promotional_shipping_rule, update_flat_shipping_rules). Usage is only implied by the resource name.

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