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

Annotations already cover the safety profile, but the description earns credit by adding what they cannot: no payment path on any route, no store and no scheduler, the lane refuses on its own kill file and lane state, no token is bought or issued, no return is promised, and cancel-any-time with funded work staying funded. Those are exactly the risk facts an agent needs before invoking a money-shaped tool.

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 core capability is front-loaded in the second sentence, but the text is a long run-on and repeats itself: "This funds work at a place you name" and "Free, keyless" each appear twice, once restated as "Cost and signer: free and keyless." Several clauses about token speculation and cancel-any-time are product copy rather than invocation guidance.

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 prose, and the annotations plus the explicit no-charge/no-custody language make the safety picture complete. The remaining gap is definitional: "the product and the ladder" is never explained, so an agent calling with zero arguments cannot predict the shape of the no-argument response.

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 all five parameters are documented in-schema, including the object form for `place` and the "never custody" note on `wallet`. The description reinforces the amount range ($1–$1,000), the period values (day/month) and the cap-plus-remainder behavior, but those repeat the schema rather than adding new parameter meaning. Baseline 3 applies.

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 concrete verb and resource: given an amount, period and place, it returns which OPEN, unfunded, claimable packets the money would back, at board order and prices, plus the place's Standing link. That is far more specific than the title's marketing phrasing ("Fund work at a place you name: the plan, and why it is not live yet"). It does not explicitly separate itself from the close siblings regen_provisioning_subscription_status or provision_plan, so an agent must infer the quote-vs-status distinction.

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?

"Call it with no arguments for the product and the ladder" plus "Omit for the product and the ladder only" gives one concrete invocation mode. However, nothing says when to choose this over regen_provisioning_subscription_status, provision_plan, or net_subscription_quote, and the phrase "the product and the ladder" is undefined jargon. Usage is implied by the amount/period/place framing rather than stated as when/when-not guidance.

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