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

With no annotations, the description carries the full behavioral burden. It does add real value by disclosing the returned fields (type, transfers, swaps, fees, plain-English description) and a concrete price of $0.002 USDC per call, which is exactly the kind of cost signal an agent needs before invoking a paid endpoint. However, it says nothing about failure behavior for invalid or unknown signatures, rate limits, or latency.

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?

Three sentences, each carrying distinct information: what it does, what it returns, and what it costs. Front-loaded with the action and free of 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?

For a simple single-parameter read tool with no output schema, the description covers the essentials: the transformation performed, the shape of the result, and the per-call cost. The only meaningful gap is what happens when the signature is invalid, pending, or not found.

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?

Only one parameter, and it is fully documented in the schema ('Solana transaction signature (base58)', coverage 100%). The description adds no format or encoding detail beyond that, so the baseline 3 is appropriate — the schema does the work.

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 and resource ('Parse a Solana transaction') plus the transformation goal ('into human-readable format'). No sibling in the list performs transaction decoding, so there is no ambiguity about which tool handles this job.

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?

Usage is only implied by the required signature parameter — an agent can infer 'use this when you have a signature and want a decoded view.' There is no explicit when-to-use, when-not-to-use, or named alternative, and no note about prerequisites such as the transaction needing to be on-chain or confirmed.

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