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

Annotations already declare the write/open-world, non-idempotent, non-destructive profile, and the description adds genuinely new behavior: the mandatory quote-then-settle handshake and the post-settlement state (a new intake stays private pending house review). It does not mention auth requirements, rate limits, or whether a failed settlement is recoverable.

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 tight sentences with no filler: scope first, then the call sequence, then the resulting state. Every sentence carries information an agent needs before invoking.

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 7-parameter mutation with no output schema, the description covers the invocation sequence and the outcome state, which is the important missing context. A little more on what the quote response contains and whether a partial/failed settlement can be retried would make it complete.

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% and the field descriptions already explain that fee_cents, price_cents, and claim_limit are server-overridden display values, so the baseline is 3. The description goes further by explaining the role of payment_payload (omit on the first call, sign on the second), which is not spelled out in 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 (fund) and resource (a private vendor intake or approved legacy posting) plus the underlying endpoint POST /v1/funding, which is concrete. It implicitly separates itself from creation-oriented siblings like post_bounty, though it never names a sibling or states the boundary 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 a clear two-phase invocation protocol: call once without payment_payload to receive x402 payment requirements, then call again with the signed payload to settle. That is actionable context, but it offers no guidance on when funding is appropriate versus enlisting, claiming, or posting a bounty.

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