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

No annotations are provided, so the description carries the full burden. It usefully discloses that this is an x402-paid endpoint (GET /api/x402/tx-receipt-decoded-json, $0.01), which is real behavioral context an agent needs before calling. However, it says nothing about auth mechanics, rate limits, or failure modes.

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?

A single compact line with the core purpose front-loaded and payment metadata bracketed at the end. Efficient, though the mixed formatting (query-param example plus pricing block) is slightly cryptic.

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 lookup with no output schema and no annotations, the description covers what is returned (receipt + decoded calldata) and the cost of the call. It lacks return-format specifics and error semantics, but is broadly sufficient to invoke correctly.

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 100% for the single tx parameter, so the schema already documents 'Base tx hash 0x...'. The description's '(?tx=0x...)' merely restates the same format, adding no value beyond the schema; baseline 3 applies.

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?

Names a specific verb+resource: fetching a Base transaction receipt plus decoded calldata. It clearly distinguishes itself from generic RPC siblings like lion_keyless_base_rpc by promising decoded calldata, though it never names siblings explicitly.

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 no when-to-use guidance, no conditions, and no mention of alternatives such as lion_keyless_base_rpc for raw receipt access. Usage is only weakly implied by the resource name and the '?tx=' example.

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