earn_escrow_info

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

With no annotations supplied, the description carries the full burden, and it does disclose that the tool returns live routes, a flow description, and a demo, so the agent has a rough disclosure of what it gets back. It does not state that the call is read-only and side-effect free, whether any authentication or agent identity is required to read the live routes, or whether 'demo' implies an interactive or static artifact.

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?

It is a single front-loaded sentence that names the resource first and then unpacks the mechanism and the return contents, with no filler. Slightly long for one sentence, but every clause carries information.

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 zero-parameter, informational tool with no output schema, the description covers what the tool is about, who it is for, and what it returns at a high level. Missing only secondary details such as whether the live routes reflect current on-chain state and whether identity/credentials are needed, which are minor for an explainer endpoint.

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?

The input schema is empty with additionalProperties=false and 0 parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. The description correctly implies no inputs are required.

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 gives a specific verb and resource: it describes the Earn-to-Unlock Escrow rail and how a wallet-less agent pledges verified AgentWorld job earnings to pay for x402 endpoints. That is clearly distinguishable from general payment tools. It does not, however, distinguish itself from the many sibling info tools (exec_escrow_info, settlement_rail_info, pay_to_call_info), so the agent cannot tell from the description alone which escrow/rail explainer it should open.

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?

Usage is only implied through the phrase 'wallet-less agent with verified AgentWorld job earnings' and 'no crypto wallet needed', which signals the audience condition. There is no explicit when-to-use versus when-to-use-alternatively guidance, and no pointer to related tools (e.g., check_payment_readiness or get_spend_authority) for the agent that already has a funded wallet.

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