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

Annotations only flag readOnlyHint=false and destructiveHint=false; the description goes further by disclosing the four on-chain/pool gates, the mutation ('mark it funded'), idempotency ('safe to call again'), and the required Bearer JWT auth. This is meaningful context beyond structured fields, though it doesn't describe failure modes or return values.

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 action and its preconditions lead, then the entry-semantics clarification, then the two operational notes (idempotency, auth). Every sentence carries load, though the chained 'and ... and ... and' conditions are slightly dense.

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 one-parameter tool with no output schema and clear annotations, the description covers preconditions, effect, idempotency, and auth. It is nearly complete; only error/failure handling is absent.

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 coverage is 100% on the single pledge_id parameter, so the schema already carries the detail ('Your pledge's uuid'). The description references 'your pledge' but adds no format or constraint information beyond the schema.

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 (confirm/mark funded) and resource (pledge deposit address) with the exact on-chain preconditions it checks. An agent can distinguish this from signet_pledge (creating a pledge) or signet_pledge_pool (pool ops) by the funding-confirmation action, though no sibling is named explicitly.

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 the implicit context (after making a pledge) and a re-use hint ('safe to call again'), but never states when to prefer this over signet_pledge, signet_pledge_pool_result, or signet_pledge_outcomes, nor any when-not-to-call exclusion.

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