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

With annotations already covering read-only, idempotent, open-world, and non-destructive behavior, the description adds useful context by naming the live data source and underlying RPC method (public Solana JSON-RPC getTransaction). It still does not discuss error behavior for missing transactions or possible rate limits.

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?

The description is front-loaded with the core operation, then lists the returned details, then states the user-facing purpose and data source. Every sentence carries useful information and there is no redundant 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?

There is no output schema, so the description carries the return-value burden, and it does so thoroughly: block time, slot, fee, success/failure, signers, programs, instruction types, SOL balance changes, and SPL token balances. Together with the annotations, an agent has enough context to call the tool 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 coverage is 100%, and the schema already documents the single signature parameter as a base58 string roughly 88 characters long. The description confirms the lookup is by signature but adds no format or syntax details beyond the schema, so 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 states a specific resource and access pattern: details of one Solana transaction by signature, and it enumerates the returned fields. It is clearly distinct from wallet-level tools, but it does not explicitly name or contrast with the closest sibling, solana_wallet_transactions.

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 use case is implied by 'Details of one Solana transaction by signature' and 'Answers what did this Solana transaction actually do.' However, there is no explicit when-to-use/when-not guidance or routing against alternatives such as solana_wallet_transactions.

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