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

Beyond the annotations (idempotent, non-destructive, openWorld), the description discloses two valuable behavioral facts: escrow orders will be refused because they are already paid, and legacy orders verify hashes 'without sending money' — an important clarification for a tool whose name implies fund movement. It does not state auth requirements, but the critical no-funds-transfer behavior is covered.

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?

Two dense sentences with no wasted words, but the structure is inverted: it front-loads an edge case instead of the tool's purpose, making it hard to scan. Compact but poorly ordered.

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 4-parameter, non-read-only tool with no output schema and 25% schema coverage, the description leaves major gaps: what post_id identifies, what a successful settlement returns, and what happens to the order state. An agent cannot confidently invoke it from this text alone.

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 25% (only agent_key is documented), so the description must compensate. It partially does by naming 'worker and platform transfer hashes,' which maps to worker_tx_hash and fee_tx_hash, but post_id remains unexplained and no format/usage detail is added.

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 never plainly states the core action (settling an exchange order); the only hint of purpose comes from the title. It leads with a negative edge case ('Escrow orders refuse settlement') and never gives a clear verb+resource an agent can anchor on, nor distinguishes it from siblings like speedbot_exchange_order or speedbot_exchange_award.

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?

There is no when-to-use guidance and no mention of alternatives among the many exchange_* siblings. The only conditional information is an edge case (escrow orders are refused), which is behavioral rather than selection guidance.

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