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

With annotations already covering readOnly, idempotent, open-world, and non-destructive behavior, the description adds meaningful context beyond them: the per-call price, free allowance, and the fact that failed transactions include error log lines. This gives the agent useful operational information without contradicting the annotations.

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?

Two sentences with no filler: the first sentence states the core behavior and output, the second defines coverage and pricing. The most important information is front-loaded, and every clause adds value.

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?

Despite lacking an output schema, the description lists the return fields in enough detail for an agent to know what to expect. The single required parameter is explained, the supported transaction categories are enumerated, and the cost is disclosed. Nothing critical is missing for correct invocation.

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 0%, but there is only one parameter and the description explains that it is a Solana transaction signature. Combined with the schema's pattern and required flag, the agent knows exactly what to supply. The description does not add extra detail about signature formats, but the schema handles that constraint.

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 uses a specific verb ('Turns') and a concrete resource ('Solana transaction signature'), then enumerates the exact output ('status, fee, programs by name, SOL and token balance changes per owner, a one-line summary'). It also scopes the tool to specific transaction types, which separates it from the sibling tools that target individual tokens, wallets, or pools.

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 description clearly communicates context by listing supported cases: swaps, pump.fun trades, LP moves, transfers, and failures. It does not explicitly name alternatives or state when not to use this tool, but for a general-purpose transaction explainer the intended usage is clear and well-scoped.

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