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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful operational context beyond them: it runs against public RPC, requires no API key, and costs $0.005 USDC per successful call via x402 — cost and auth are things an agent planner should know before invoking.

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 core decode sentence is front-loaded and efficient, but the tail is padded: 'Unique on Bazaar' is pure marketing noise, and the price plus the raw HTTPS URL duplicate commercial metadata that an agent does not need in order to call the tool.

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-signature lookup with rich annotations and no output schema, the description enumerates the returned fields (status, fee, compute units, instructions, inner instructions, account keys, logs), which substitutes well for an output schema. Only error behavior for failed/unknown signatures is unmentioned.

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?

One parameter at 100% schema coverage (base58 tx signature), so the schema already carries the meaning. The description adds nothing about format, signature length, or behavior for invalid signatures, so it meets but does not exceed the baseline for full coverage.

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 (Decode) plus the exact resource (Solana mainnet transaction) and enumerates the decoded fields returned, which lets an agent distinguish it from evm_tx_info or sol_balance without opening a schema. It stops short of explicitly naming a sibling it is not.

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?

No statement of when to use this versus alternatives, no prerequisites, no edge cases. The remaining sentences cover pricing and an alternate HTTPS endpoint, which is commercial framing rather than selection guidance.

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