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

Adds context the annotations cannot carry: pending/unknown hashes return 404 and are uncharged, successful calls cost $0.01 via x402 USDC or a card key with the first 25 free, and the 'each call is charged, so repeats are not free' line explains why idempotentHint=false. The 'reads or computes only and changes nothing' sentence mostly restates readOnlyHint, but the payment/failure semantics are genuinely new information.

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?

Front-loaded with purpose and return contents, then usage, then input contract, then pricing — a sensible order with little waste. The pricing/free-tier clause is somewhat long relative to its selection value, but it is not filler.

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?

There is no output schema, and the description compensates by enumerating the returned receipt fields, so an agent knows what it will get without guessing. With a single fully-documented parameter and error/fee behavior spelled out, nothing needed to call this 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% for the single hash parameter, so the baseline is 3; the description earns one more by restating the format inline ('0x-prefixed 64-hex hash'), supplying a concrete example hash, and documenting the failure behavior for a well-formed but pending/unknown hash.

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/resource ('Transaction receipt on Ink') and enumerates exactly what comes back (status, gas used, effective gas price, fee in ETH, log count, contract created). It also explicitly separates itself from the sibling ink_tx ('for sender, value and calldata use ink_tx'), so an agent can choose without opening either 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?

'Use to confirm a payment or call went through' gives the positive case, and 'for sender, value and calldata use ink_tx' gives the named alternative with the condition that selects it. The pending/unknown → 404 behavior adds a concrete exclusion case.

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