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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered, yet the description still adds substantive behavior: known-program layouts (System, Compute Budget, SPL Token, Token-2022, ATA, Memo) versus IDL-based decoding for everything else, plus inner-instruction tracing and per-owner balance deltas. That tells the agent how deep the analysis goes and where it may be weaker (non-IDL programs). It omits failure modes for a bad signature and any rate/cost limits, so it is not a 5.

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?

Front-loaded with the core claim ('Every instruction of a Solana transaction by name') and then enumerates the returned sections, ending with concrete user questions. The middle is one long semicolon-chained sentence, which is dense but each clause maps to a distinct output section, so little is wasted.

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?

With no output schema, the description carries the return-value burden and does so thoroughly, enumerating every section the agent will receive. For a one-parameter decode tool that is nearly complete; only invalid-signature behavior and any chain/scope caveats are missing.

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?

There is a single parameter and schema coverage is 100%, with the schema documenting 'base58' format, so the baseline is 3. The description adds nothing about the signature argument itself, which is acceptable given the schema already carries the format.

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 resource (a Solana transaction) and precisely what it produces: named instructions with arguments and labelled accounts, inner instructions, per-owner balance deltas, signers/compute/fees, and account sign/write status. That is far more than a restated title. It stops short of 5 because it never distinguishes itself from the similarly-named sibling tx_explain, which an agent could easily confuse with this one.

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 closing sentence supplies concrete trigger phrasings ('what did this transaction do?', 'decode this swap', 'what were the arguments?'), which gives real usage context. However, there is no when-not guidance and no routing away from tx_explain or account_decode, so the agent must infer the boundary itself.

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