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

The description is rich in behavioral context far beyond the annotations. It discloses crucial operational facts: billing (cost per call, first 25 free, failed calls free), execution guarantee (reads/computes only), and edge case behavior (unknown hash returns 404, uncharged).

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 paragraph is dense, but every sentence carries essential, non-redundant information, progressing logically from basic function to usage guidelines, then behavioral specifics and finally cost/operational constraints. It is highly structured.

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?

Given the complexity of a blockchain interaction tool, the description is fully comprehensive. It covers input format, operational safety, alternative routing, and the economic constraints of using the tool.

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?

While the schema coverage is 100%, the description reinforces the critical input format requirement—a '0x-prefixed 64-hex hash.' This is an essential semantic detail that ensures correct tool invocation.

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 purpose is perfectly clear: 'Look up a Mantle transaction by hash.' It achieves maximum clarity by simultaneously listing all transaction components it reveals and explicitly directing the user to two specific sibling tools for related information (mantle_receipt and mantle_logs).

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 tool provides excellent usage guidelines by specifying exactly which alternative tool to use for specific needs. It guides the user to mantle_receipt for success/failure/fees and mantle_logs for events, preventing tool confusion.

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