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

With no annotations the description carries the full safety burden, and it does so well: it declares the operation read-only by excluding wallet, signing, broadcast, custody, and execution actions, and it discloses that raw instructions and logs are excluded from the response. It stops short of error modes or rate-limit behavior, so it is strong but not exhaustive.

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?

Purpose and scope are front-loaded in the first sentence, followed by usage, exclusions, and auth/retry notes in a logical order. It is dense and the payment-challenge/credentials sentence is operational overhead, but each sentence conveys distinct information.

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?

There is no output schema, so the description properly compensates by enumerating the returned fields (status, slot, block time, fee, SPL-token owner deltas, USDC deltas). Combined with the explicit side-effect exclusions and the cross-chain alternative, an agent has what it needs to invoke it 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%, so the schema already documents each parameter's format and the recipient/amountAtomic/payer interdependencies. The description reinforces the verification intent but adds no syntax or format detail beyond the schema, so the 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?

The description names a specific verb (Inspect) and resource (one finalized Solana mainnet transaction signature), enumerates the normalized fields returned, and explicitly contrasts itself with the sibling `transaction_receipt` for Base/Ethereum. An agent can distinguish it from the other receipt/wallet tools without opening the 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?

It states the trigger for the optional verification mode ('Supply recipient, amount, and optional payer when an exact settlement claim must be verified') and names the alternative tool plus the chain condition that selects it. It also tells the agent to retry the identical authorized arguments and credential, which is actionable routing guidance.

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