ebay_get_shipping_locations

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 useful behavior beyond that: it enumerates what is returned (regions, countries, special locations) and explains the localization nuance for EBAY_CA/EBAY_BE. No auth, rate-limit, or pagination notes, but value is added beyond the annotations.

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?

Three front-loaded sentences with no filler; the core purpose leads, followed by localization and downstream use. Minor overlap with the schema's acceptLanguage text, but overall tight and well ordered.

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?

With no output schema, the description does describe the return content (regions, countries, special locations) and how consumers should use it. For a two-parameter read-only metadata call backed by a full-fidelity schema and annotations, this is nearly complete, lacking only pagination/size expectations.

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 coverage is 100%, so both parameters are already documented. The description's acceptLanguage explanation largely restates the schema description (fr-CA/fr-BE/nl-BE mapping, EBAY_CA falling back to English), adding little new syntax or format detail. Baseline 3 applies when the schema carries the semantics.

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?

Clear specific verb+resource: 'list the regions, countries and special locations a seller can ship to on a marketplace.' An agent can identify the tool's output. However, it never explicitly distinguishes itself from close siblings like ebay_get_exclude_shipping_locations, so routing among the shipping-location tools is left to inference.

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 downstream context: 'Use the returned values when configuring fulfillment policies (ebay_create_fulfillment_policy),' naming the consuming tool. Also frames the acceptLanguage conditional per marketplace. It stops short of stating when-not-to-use or explicitly contrasting with the exclude-locations sibling.

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