ebay_get_handling_times

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

readOnlyHint=true already declares this is a safe read, so the bar is low, yet the description adds real context: it identifies the Metadata API, explains what a handling time represents, and discloses the 'extended' flag and the localization constraints. It does not mention auth or rate limits, keeping it below 5.

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 sentences, front-loaded with the core purpose before the parameter detail and downstream usage. Dense but no filler; slightly repetitive with the schema on acceptLanguage.

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, and the description compensates by sketching the return (handling times with an extended flag) plus the downstream consumer. Combined with the read-only annotation and complete schema, an agent has enough to call it correctly, though return-shape detail is thin.

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 in the schema, and the description largely restates the acceptLanguage localization rules. It adds only marginal meaning over the schema, matching the 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 (list) and resource (handling times) with scoping ('a marketplace allows') and even defines the concept: 'maximum business days to ship after cleared payment, flagged when extended'. An agent can distinguish it from fulfillment-policy tools and other metadata listers 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?

Explicitly routes the agent to a downstream use: 'Use the returned values when configuring fulfillment policies (ebay_create_fulfillment_policy).' It also tells when to supply acceptLanguage per marketplace. It stops short of stating when not to call this tool, so it is not a full 5.

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