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

With only readOnlyHint=false provided, the description goes well beyond it: it warns the call 'changes stored state and is not safe to repeat blindly' (idempotency), states the listing is 'Immutable and chained' (no undo), and flags the trillion-fold decimal trap between USDC (6dp) and 1F916 (18dp). Those are exactly the destructive/irreversibility facts an agent cannot infer from annotations.

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?

Front-loaded with the four required inputs, then asset semantics, then the WRITES warning last; each sentence carries content. It is dense and packs several parenthetical clauses, but there is little pure filler, so it stays near the optimal size for a 10-parameter mutation.

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?

No output schema exists, and the description compensates by explaining funding semantics, immutability, decimal units, the funder/verifier roles, and the listing-<id> binding. Gaps remain on success behavior (what identifier returns), authorization requirements, and how to cancel, but nothing essential to calling it correctly is missing.

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 80%, so much is already documented, but the description adds real meaning: the condition must be evaluable by a stranger, the price is 'atomic units of the asset you name,' and the default asset/decimals are spelled out. It is weakened by referencing an asset choice and 'payees bind against row listing-<id>' that have no corresponding schema parameter, leaving the mechanism unexplained.

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?

Specific verb+resource: 'Post a task anyone can fund' and it enumerates the required ingredients (title, condition, atomic price, expiry). It also carves the concept away from adjacent ideas ('funder's public statement, not escrow and not a maintainer endorsement'). However, it never names a sibling tool (post, publish_offer, listings, withdraw_listing) to route the agent, so it stops short of the 5 bar.

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?

There is contextual framing about what this is not (not escrow, not endorsement) and a funder-wallet hygiene warning, which implies the appropriate situation. But there is no explicit when-to-use-vs-alternative routing, no statement of prerequisites, and no guidance on how this differs operationally from `post`, `publish_offer`, or how to undo it (withdraw_listing).

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