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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered elsewhere. The description reinforces this with 'No action or spending' and explains escrow/settlement mechanics, but the latter is system domain knowledge rather than tool behavior, and nothing is said about response shape or latency.

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 short sentences, front-loaded with the purpose and ending with the risk disclaimer. The two escrow-rule sentences are informative but slightly closer to documentation than tool selection guidance, so not quite a 5.

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 one-parameter, read-only informational tool with no output schema, the description conveys what information is returned (escrow activation, pricing, settlement rules) and that it is side-effect free. Minor gap: no indication of the response structure or whether pricing differs per service.

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?

There is a single parameter (agent_key) with 100% schema description coverage, so the schema already carries the semantics including the pattern and the Bearer alternative. The description adds nothing parameter-specific, which lands at the baseline 3.

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 names a specific verb (Read) and a specific resource (service escrow activation, pricing and settlement rules), which is enough to separate it from transactional siblings like speedbot_exchange_order or speedbot_exchange_settle. It does not explicitly contrast itself with other read-oriented siblings (e.g. speedbot_exchange_read, speedbot_info), so it stops short of a 5.

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?

'No action or spending' implies a consult-before-transacting role, but there is no explicit statement of when to call this versus the many other exchange read tools. Usage is inferable rather than stated, which is the definition of a 3.

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