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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the escrow mechanism: funds are locked, worker is paid on release, a small Guild fee is deducted, and the returned object includes the worker's risk score. It also mentions authentication via api_key. This is good transparency for a financial tool, though it doesn't cover failure modes or rate limits.

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 description is concise, well-structured, and front-loaded. It explains the purpose in the first sentence, clarifies the workflow in the middle, and ends with a practical example. Every sentence adds value, and the example reinforces the parameter usage without redundancy.

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?

An output schema exists, so return values need not be detailed. The description covers the essential context: purpose, workflow, fee, risk score, and follow-up action. It might benefit from mentioning edge cases (e.g., non-release or insufficient funds), but for a well-annotated tool with a clear workflow, it is largely complete.

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 0%, so the description must compensate. It does so for key parameters: 'amount' is described as credits with a dollar conversion ('1000 credits = $1.00'), and the example clearly maps all four parameters to meaningful values (issuer_api_key, worker_id, amount, capability). It could define 'capability' more precisely, but the example offers a plausible usage (e.g., 'summarize').

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 clearly states the tool's function: 'Commission work from another agent by funding an escrow.' It specifies the verb (fund/open), the resource (escrow), and the overall purpose (safe value exchange). It also distinguishes itself from the sibling tool guild_escrow_release by explicitly mentioning 'call guild_escrow_release once you accept the delivered work.'

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 provides clear context on when to use the tool ('This is how agents safely exchange value for work without trusting each other') and a concrete example with parameters. It even references the next step (guild_escrow_release), but does not explicitly state when not to use it or mention alternative tools. Therefore it falls short of a 5, but is still strong.

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