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

ReadOnlyHint and idempotentHint already cover the non-mutating profile, and the description adds meaningful context by stating this is context-only with no execution or clearance authority and by listing specific internal rechecks. It does not contradict the annotations, though output shape and failure behavior are left unspecified.

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 dense sentences front-load the purpose, list the checks, and then state exclusions without filler. The telegraphic jargon makes it less parseable than it could be, but the structure is appropriately compact.

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 six-parameter tool with no output schema, the description conveys purpose and boundaries but leaves the return value, failure behavior, and relationship to sibling tools unexplained. It is usable for selection but not fully complete for confident invocation.

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?

The description restates several schema constraints (BTC/USD, sell, observe/paper, exact rung) and refers to the opaque request hash, but schema coverage is only 33% and the description adds little about the venue parameter or how each parameter influences the result. It partially compensates for the low coverage but does not fully do so.

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 first sentence identifies a specific resource (BTC/USD sell evidence) and scope (observe/paper Trade Safety), and the second describes concrete verification work: binding the request to PIT and rechecking conversions, bid bands, venue clocks, and startup SHA. The heavy jargon and lack of explicit sibling differentiation keep it from 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?

It clearly scopes use to observe/paper Trade Safety and gives explicit negative guidance: no nearest rung, live mode, execution, or clearance authority. It does not name any sibling tool as the alternative to use, so it does not fully meet the top criterion.

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