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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true), so the description's added value is what it says beyond that: the tool produces an unsigned payload for local signing, must never receive keys or preimages, and one specific funding failure mode. It does not describe whether the endpoint creates any server-side state, but the safety and return-shape context is substantive.

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?

Information is front-loaded and dense with no filler, moving from endpoint to required fields to the return value to the safety constraint. The leading 'POST /jobs/:id/fund' restatement is the only low-value token.

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?

With no output schema, the description correctly explains what comes back (an unsigned extrinsic to sign locally), plus the key prerequisite and failure code. The main remaining gap is the follow-up step for submitting the signed payload, and how 'rail' defaults when omitted.

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 75%, and the schema already documents 'to' as payee SS58, 'from' as funder SS58, and 'rail' values. The description only reinforces that flop-devnet requires body.to and from, adding marginal meaning; jobId remains undocumented in both places.

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?

The description states a specific verb and resource -- funding a job escrow via POST /jobs/:id/fund -- and clarifies that it returns an unsigned 'hasStation.openEscrow' extrinsic rather than submitting it. That distinguishes it from write-side siblings like crew_submit_signed, though it does not explicitly name any sibling.

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?

It gives a concrete precondition (fund the payee existential deposit first, else the claim fails with PAYEE_DEAD_ACCOUNT) and notes flop-devnet body requirements. However, it never says when to choose this over crew_build_unsigned or what to do after signing (presumably crew_submit_signed), leaving workflow routing implied.

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