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

Goes meaningfully beyond the annotations: it discloses that matching escrows funds from the wallet immediately under machine speed versus deferring to provider approval under human speed, and documents the 409 failure condition. It omits the non-idempotency consequence (idempotentHint=false implies a repeat call may escrow a second time) and any amount/limit context, which for a money-moving call is a notable gap.

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?

Three compact sentences with zero filler; the action is front-loaded and the escrow/approval and error details follow in priority order.

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?

An output schema exists, so return values need no explanation, and the single parameter is fully documented in the schema. What remains thin is the cost/escrow magnitude and repeat-call behavior for a mutation tool, though the core behavior is adequately covered.

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 coverage is 100%, so the schema already carries the meaning. The description reinforces ownership ('YOUR') and openness of the request, but adds no format, sourcing, or lookup guidance 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 ('Match') and scoped resource ('one of YOUR open requests'), which separates it from the generic market_match and from market_request. The 'rematch' framing and the 'now' emphasis imply re-triggering a match, but it never explicitly contrasts with market_match or market_request, so the sibling boundary is left partly to inference.

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 possessive 'YOUR open requests' and the 409 note imply the precondition (you must own an open request) but do not state it as a rule or name alternatives such as market_match or market_request_rematch_withdraw. Usage is inferable rather than prescribed.

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