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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds far more: nothing commits funds at creation, per-step and whole-chain screening, a combined spend check, worker-arranged handoffs inside caller-set windows with a two-sided code, and automatic payment 24 hours after each middle handoff unless reviewed. These are the consequential behaviors an agent needs before calling a mutating 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 opening sentence is front-loaded and dense with the key mental model; every later sentence carries actionable information. Slightly penalized because the workflow steps and the "Not for the hosted console agent" exclusion are appended after the behavioral details rather than grouped with usage 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?

For a complex 6-parameter, 5-required creation tool with no output schema, the description covers process, sequencing, payment timing, safety gating, and even the return shape ("Returns the chain as get_chain_status does"). Nothing material is left for the agent to infer.

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%, so the baseline is 3, but the description adds operational meaning to the parameter model: budgets across steps are checked together, handoff windows are the interval the workers choose from, and staffing_deadline semantics (nothing commits until all steps accept). It does not add format-level detail beyond the schema, so it stops short of a 5.

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 concrete verb+resource ("Create a chain") and immediately defines the distinctive model: one job done by several workers in turn with a physical item handed between steps. This clearly separates it from siblings like post_task (single task), make_offer, and offer_chain_link (per-step staffing).

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 spells out the follow-on workflow explicitly ("find workers with search_workers or find_workers_by_skill with chain_ok=true, then offer_chain_link for each step"), states the gating rule ("Nothing starts until every step has accepted"), and includes an exclusion ("Not for the hosted console agent"). When-to-use and when-not-to-use are both present.

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