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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful context beyond them: the tool only covers confirmed transactions, it reports both success and error outcomes, and the data is public on-chain with a "not advice" disclaimer. Rate limits and failure modes are unstated, keeping it below 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?

One dense sentence front-loads the verb and resource, then lists the return fields; a short trailing clause covers data provenance. Nothing is padded or redundant.

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 single-parameter read tool with no output schema, the description compensates by enumerating what comes back (status, time, fee, signers, programs, balance changes per account), and annotations cover the safety profile. An agent has everything needed to call and interpret it.

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 with 100% schema description coverage, including a base58 pattern, so the schema carries the parameter burden. The description only restates that lookup is "by signature," adding no format or validation detail 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?

States a specific verb and resource ("Look up a confirmed Solana transaction") and then enumerates the exact payload: status, time, fee, signers, programs, and per-account SOL/token balance changes. This clearly separates it from siblings like solana_swap_transaction (which constructs a swap) or solana_wallet_balances (which reads balances) without needing to open any schema.

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 triggering condition is explicit: you must have a transaction signature, and the target is a *confirmed* transaction, implicitly excluding pending/failed-submission queries. It never names an alternative tool or a when-not case, so it stops short of a 5.

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