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

The annotations are uninformative (readOnlyHint=false, destructiveHint=false are the defaults and sit oddly against the title's 'read-only' claim), so the description has to carry the load — and it does add real context: public/no-login access and the lifecycle semantics that give 'phase' and pledge status meaning (cancel until lock, then BURNED or RELEASED, auto-release at deadline). It stops short of error behaviour for a bad pool_id or any rate/limit notes, so not a 5.

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 sentences, front-loaded with the read scope and the returned fields before the domain background. The second sentence is dense but earns its place by defining the vocabulary (phase, BURNED/RELEASED, deadline) an agent needs to interpret the response. Slightly long for a single-parameter read.

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, and the description compensates by listing the returned fields and the possible phase/status values, which is the main thing an agent needs. What is missing is failure behaviour (unknown pool_id) and how the organiser meta is shaped; minor gaps for a read-only single-id lookup.

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?

Only one parameter, and schema description coverage is 100% ('The pool's uuid'), so the schema already carries the semantics. The description adds no format, prefix, or lookup guidance for pool_id beyond what the schema states — baseline 3 is correct.

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 and resource ('Read one pledge pool') and then enumerates exactly what comes back: stake token, stake size, lock time, release deadline, phase, organiser meta and every pledge with status/addresses/memo/reference. This clearly separates it from signet_pledges_mine (your own pledges), signet_pledge_pool_open / _cancel / _result (mutations and outcome) without the agent needing to open any schema.

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 states the access precondition ('Public; no login needed'), which is genuinely useful, but gives no explicit when-to-use routing against the obvious siblings (pool_result for the outcome, pledges_mine for your own entries). Usage is only implied by the field list, so this is minimum-viable rather than directive.

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