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

Beyond the readOnly/idempotent/destructive annotations, the description adds valuable behavioral context: it is free and keyless, it can reveal the caller's role, its possibleNextSteps is non-authoritative, and user-supplied fields arrive fenced as untrusted stranger text. No contradiction with 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?

Three dense sentences, each earning its place: the first defines scope and payload, the second explains optional wallet behavior and its caveat, the third adds a critical trust boundary. Information is front-loaded and there is no filler.

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 output schema present, the description need not restate return formats. It covers access constraints (keyless/free), parameter semantics, the authoritative relationship to prepare_chain_step, and data trust issues. The description is complete for an agent to call this tool correctly.

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 already 100%, so baseline is 3. The description adds meaning beyond the schema by explaining that chain selects the live EWP deployment, that wallet optionally reveals role and suggested next steps, and that workId is scoped to 'this chain.' This is substantive added value.

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: read one job from the public EWP contract on Base or Robinhood Chain. It enumerates the exact fields returned and the chain-specific scope, which clearly distinguishes it from broader job tools like work_status or get_work_packet.

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?

The description gives clear context for when to use the tool (live keyless read on Base or Robinhood) and explains the optional wallet behavior for learning role and next steps. It also warns that possibleNextSteps is informative only and that prepare_chain_step is authoritative, providing an explicit exclusion, though it does not name sibling alternatives directly.

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