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

With no annotations, the description must carry the full behavioral burden. It does disclose one genuinely important trait — that payment/escrow limitations are stated explicitly and that status must not be read as proof of payment — but it says nothing about freshness, whether the status is read-only (only implied by 'Read'), or what the response contains.

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 the core purpose front-loaded and a critical safety caveat second. No filler, no repetition of the title.

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 are no annotations, no parameters, and no output schema, so the description is the only source of information about what this tool returns — yet it never sketches the shape of a 'market status' response. It covers the purpose and the payment caveat adequately but leaves the agent guessing about the returned structure.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description neither helps nor hurts parameter understanding.

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 gives a specific verb ('Read') and a concrete resource scope: current market availability plus payment/escrow limitations. However, 'market availability' is somewhat abstract (availability of what — the service, listings, agents?) and nothing distinguishes it from siblings like market_in_one_call or integration_guide.

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?

The line 'Never treat an order as paid' is an operational rule attached to reading this status, which implies the tool should be consulted before assuming payment state. But there is no explicit when-to-use framing, no mention of when to prefer market_in_one_call, and no stated preconditions for calling it.

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