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

The annotations already declare readOnlyHint=true, idempotentHint=true, and the 'Read' verb is consistent with them. The description adds non-obvious behavior the annotations cannot: the status is 'quorum-backed' rather than a simple node read, and it reveals that preparation tooling only opens when the exactly permitted marketplace is unpaused — a meaningful gating behavior for agents planning transactions.

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 tight sentences with front-loaded intent and no filler; the first sentence names the resource, the second adds the gating condition. The second sentence's phrasing ('for the exact unpaused, promised marketplace') is slightly awkward, costing a minus.

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?

For a zero-parameter tool with an output schema and strong annotations, the description carries a light context, and it covers the two things an agent needs: what the status describes (market and transfer validator readiness) and why it matters (preparation opens only in the exact permitted state). The only real gap is explicit sibling differentiation, which would fully close the remaining ambiguity.

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, which gives a baseline of 4 per rubric, since there is no parameter surface for either schema or description to document. No parameter-semantics burden falls on the description.

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 first sentence names a specific verb and resource: 'Read quorum-backed Ethereum market and transfer-validator readiness,' and the title pins it to the 'live NFH Ethereum marketplace status,' which is the intent of the tool. The 'quorum' and 'Ethereum/mainnet' framing hints at how this differs from get_internal_marketplace_status or get_market_status, though the distinction is not spelled out.

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 second sentence implies when to call this — 'preparation opens only for the exact unpaused, permitted marketplace' — suggesting agents should check this before prepare_mainnet_* operations. But no sibling is named explicitly and no conditions for choosing this over get_internal_marketplace_status or get_market_status are stated, so Usage Guidelines rest on interpretation.

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