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

Annotations already declare readOnlyHint and idempotentHint; the description adds valuable behavioral context by explaining the response perspective ('in the business's words') and its components: proposal, terms_sha, who is waiting, available next actions, and conversation thread. This goes beyond the annotations without contradicting them.

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 key action and resource are front-loaded, and every clause adds substantive detail. It is one long sentence with a heavy colon-separated list, which is efficient but slightly dense; a little more structural separation would improve scannability.

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?

There is no output schema, so the description rightly carries the burden of explaining what the response contains, and it does so well. It omits edge cases like missing or nonexistent items and exact error behavior, but the read-only annotations plus rich return description make the tool usable for correct invocation.

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 75% and the schema already explains key, pass, and access_token in detail. The tool description itself adds no parameter-specific guidance, and item_id has no schema description, but its meaning is self-evident. A 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 uses a specific verb and resource: 'get' the 'current state of an item'. It enumerates what the status contains (offer with terms_sha, who it waits on, next actions, thread), which clearly separates it from the mutation and creation siblings like create_order, accept_offer, and send_message.

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 anchors usage to 'an item you created' and to the waiting state ('waits for your person to answer'), so an agent can infer this is the read-status/polling tool after creation or an offer. It does not explicitly name when-not-to-use or alternatives, so it stops short of a 5.

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