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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still earns credit by disclosing the auth scope required, the concrete 403 failure mode for unclaimed sandbox workspaces, and the 30-day window on negotiations data. These are failure and scope facts an agent cannot get from 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?

Front-loaded with the verb and purpose before the contents list and the two prerequisites. The middle enumeration is long but each item is a distinct data class an agent may be looking for; only slight tightening would be possible without losing information.

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, so the description must describe the return contents, which it does item by item. Combined with stated auth scope and failure behavior, an agent has everything needed to decide whether to call it and to interpret a 403.

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?

Zero parameters, so there is nothing for the description to disambiguate – baseline 4. No parameter claims are made that could mislead.

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 (Read) and a precise resource (how your workspace takes offers and counter-offers), then enumerates the concrete contents: on/off flag, public handle, rounds, concession and expiry limits, products with list and floor prices, 30-day negotiations, and public URLs. The read-only framing makes it distinguishable from the sibling set_offer_settings, and the enumeration prevents confusion with get_offer_terms or discover_offers.

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?

Preconditions are explicit: a Last Price credential with routing read scope, and a claimed workspace (self-registration sandbox key is refused with 403). What's missing is explicit routing to alternatives – it never says to use set_offer_settings to change these values or get_offer_terms for a single offer. Strong context, but no named when-not/alternative.

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