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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds one piece of real context beyond that: the values are marketplace-accepted (i.e., a constrained reference set) and the connected shop is demo/sample data, warning the agent the data is not production.

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?

Two short sentences with no padding, and the core purpose is front-loaded. The 'Works on: Demo shop (sample data)' clause is slightly cryptically formatted, which keeps it just short of a 5.

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?

An output schema exists, so return values need no explanation, and the annotations cover the safety profile. What is missing is the relationship to offers_update_handling_time and any note on whether these values are paginated or exhaustive — an agent has enough to call it, but not enough to know why it should.

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 'account' parameter, and the schema already explains it is sourced from list_accounts and is optional for single-account setups. The description adds nothing further, so the baseline 3 is appropriate.

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?

The description states the resource precisely ('Handling-time values the marketplace accepts') and tags it as a catalog lookup, which separates it from the mutation sibling offers_update_handling_time. The verb is implied via the title rather than stated in the body, but the meaning is unambiguous.

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?

There is no statement of when to call this versus alternatives. The obvious companion, offers_update_handling_time, is never referenced even though this catalog almost certainly supplies valid values for it. The only usage-like note is a scope fact ('Works on: Demo shop').

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