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

No annotations are present, so the description carries the behavioral burden. It discloses the $0.001 cost and the receipt fields returned, which is useful operational information. However, it does not state read-only behavior, error handling for missing transactions, or any rate limits, leaving a partial gap.

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?

The description is very short and front-loads the essential return fields. The telegraphic style with question marks is compact but still informative. It earns its place with the cost disclosure, though a bit more polish around the field names would help.

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?

The presence of an output schema reduces the need to document return values, and the tool is a simple status lookup. However, with no annotations, no usage guidance, and no parameter semantics in the description, the overall context is only minimally adequate. An agent could likely call it correctly using the schema, but not with full confidence about behavior or alternatives.

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 0%, and the description does not explain the chain, tx_hash, or agent_id parameters. It mentions response fields like block, gas, and cost, which are not inputs. The name and schema provide the only hint that tx_hash is the key input, so the description adds minimal parameter-level value.

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 clearly identifies the tool as returning a transaction receipt with mined status, success, block, gas, and cost. The verb is implied rather than explicit, but the resource and fields are specific enough to separate it from generic tools. It does not explicitly name a sibling for differentiation, so it falls 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?

The description gives no guidance on when to use this tool versus alternatives like ddg_tx_smoke_test or ddg_order_status. There is no stated context, prerequisite, or exclusion. The agent must infer usage from the name alone.

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