nullclear_crypto_market_oracle

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond them: it is spread-verified across multiple exchanges, emits cryptographic invariant receipts, needs no configuration, and is capped at 10 free daily calls.

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 sentences, front-loaded with the core action and resource. The pricing/configuration note in the second sentence is relevant and compact; nothing is wasted.

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?

With no output schema, the description does enough by noting the return includes spread-verified prices and cryptographic receipts, and it flags the free-call limit. It is slightly thin on the exact receipt format, but for a low-complexity read tool with full annotations this is close to 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 description coverage is 100% for the single 'pair' parameter, so the baseline is 3. The description does add one supported value not present in the schema examples (BASE/USDC), but otherwise does not expand on parameter semantics.

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 gives a specific verb ('Fetch') and resource ('multi-exchange spread-verified crypto spot prices') and enumerates the supported pairs, making the tool's function immediately legible. It does not explicitly contrast itself with the sibling tools (reputation, escrow, token audit, etc.), but the resource is distinct enough that confusion is unlikely.

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 guidance on when to use this over the sibling NullClear tools, nor any stated conditions or prerequisites beyond 'zero configuration'. The mention of '10 free daily calls' hints at a rate limit but does not tell the agent when this tool is the right choice.

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