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

Annotations are empty, so the description bears full responsibility. It says 'read', implying read-only, but doesn't disclose it explicitly. It also doesn't mention error handling, network implications, or whether the entire receipt is returned. The field list is a useful hint but not enough to understand side effects or safety.

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 a single sentence, front-loads the verb and resource, and lists the receipt fields in a compact way. Every word adds value, and there is no redundant phrasing.

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 one-parameter read tool with no annotations or output schema, the description covers the core purpose adequately but omits any mention of typical edge cases like a non-existent transaction or large log data. More importantly, it doesn't clarify that this is a safe, read-only operation, which would set appropriate expectations. It's the minimum viable description.

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 schema only provides a name and pattern for `hash`, and the description's field list (status, value, gas...) implies the hash is a transaction hash, providing helpful context. However, the description doesn't directly describe the `hash` parameter or formats. Since the parameter is simple and the description adds some context, this is a pass.

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 states a verb ('Read and summarize'), a specific resource ('a Base transaction plus receipt') and the exact receipt fields covered ('status, value, gas, fee, logs and contract creation'). This distinguishes it from the sibling 'base_*' tools, but it doesn't explicitly name an alternative, so it loses one point.

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 about when to use this tool versus siblings. While the 'base_' prefix suggests a family, there's no explicit mention of alternatives or conditions. The agent must infer from the tool name and schema.

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