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

With only two thin annotations, the description carries the behavioral load and does it well: it discloses the destination allow-list (sign-in wallet, payout wallet, address that funded the pledge), the `locked` refusal, and the side effect that withdrawing a funded pledge before lock cancels the entry. Minor tension with destructiveHint=false since funds leave the account, but the destinations are provably the caller's own, so it is not a true contradiction.

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?

Dense but front-loaded: the without/with distinction leads, followed by refusal and side-effect caveats, ending with the auth requirement. Sentences are somewhat long and nested but each carries unique information; nothing is filler.

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, and the description compensates by explaining what the query mode returns (withdrawability, holdings, allowed destinations) plus auth and refusal behavior. It does not describe what the withdraw mode returns, a modest remaining gap for a mutation path.

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 100%, so a 3 is the baseline, but the description goes further by enumerating exactly which destinations are permissible for `to` and clarifying that omitting it lists them. This adds real decision-relevant meaning beyond the schema's terse 'One of the allowed destinations.'

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 (withdraw) and resource (pledge), and explicitly splits the dual mode: without `to` it is a query, with `to` it empties the account. An agent can distinguish the two invocation intents without opening the 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?

Gives clear conditions for each mode (omit `to` to inspect, supply `to` to withdraw), names a refusal condition (`locked` while the pool is locked with no outcome), and states the auth prerequisite. It does not, however, point at sibling tools such as signet_pledge_pool_cancel or signet_pledge_confirm for related flows.

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