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

The description adds useful behavior beyond the annotations: direct mode has no custody, escrow mode returns a fee quote and unsigned approve plus createAndFundFor transactions, and omitting serviceId returns open_job transactions. The annotations already cover mutability and safety hints, and the description is consistent with them.

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 compact and front-loads the mode split, with no obvious filler. Its telegraphic fragments make it slightly less clear than a more structured explanation would be.

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?

This is a complex 10-parameter mutation tool with low schema coverage, and the description omits meaning for most parameters. The output schema covers return values, but the description remains insufficient for confident invocation despite the annotations.

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 description coverage is only 20% across 10 parameters, and the description explains only mode and serviceId semantics. It leaves spec, buyer, amount, skillId, provider, specHash, evaluator, and deadlineSeconds without added meaning beyond their basic schema types.

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 operation, place_order, and explains the two execution modes: direct payment requirements versus escrow fee quote and unsigned transactions. It does not differentiate this tool from sibling tools such as get_order or claim_listing.

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 explains the behavioral distinction between direct and escrow modes and what happens without serviceId, which implies when each path applies. However, it gives no explicit guidance on choosing between this tool and alternatives, nor on prerequisites or when not to use it.

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