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

Goes well beyond the annotations by disclosing that an unknown hash returns 404 and is uncharged, that each call is billed ($0.01 via x402 USDC or card key, first 25 free, failed calls free), and that repeats are not free — which usefully explains the idempotentHint=false. The only omission is what the successful payload looks like in structure, which the field list partially covers.

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?

Purpose and field list are front-loaded, and the sibling routing follows immediately. The pricing and free-tier sentence is long but earns its place because the tool is metered; the inline example hash is the one element that could be trimmed.

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 single-parameter, no-output-schema read tool, the description covers what comes back, error behavior for unknown hashes, cost model, and which sibling to use instead. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% and the schema already documents the single hash parameter as a 0x-prefixed 64-hex string, so the description largely restates it. The concrete example hash and the 404-on-unknown outcome add a little meaning, but not much beyond the structured field.

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?

States a specific verb and resource ('Look up a Gnosis transaction by hash') and enumerates the returned fields (sender, recipient, value in xDAI, nonce, gas limit, selector, block). It explicitly separates itself from gnosis_receipt and gnosis_logs, so an agent can pick it without opening any schema.

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?

Gives concrete when-to-use ('to see what was sent or whether it exists') and names the alternatives with the condition that selects each: gnosis_receipt for success/failure and fees, gnosis_logs for emitted events. Nothing is left to inference.

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