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

Annotations already mark the tool read-only, idempotent, and non-destructive. The description adds behavioral value by specifying the response characteristics: plain-English description, type, source protocol, fee, and timestamp per transaction. It does not discuss rate limits or deeper API details, but those are not required given the annotations and schema examples.

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 definition is tightly written: one sentence for core purpose, one sentence for differentiation, and one illustrative example. No wasted words, and the most important information is front-loaded.

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 tool with no output schema, the description adequately describes the return content and the call shape, and the schema covers parameters and examples. It could be more explicit about the raw response structure or API limits beyond the schema, but nothing essential is missing for an agent to call 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 address, limit, and _apiKey. The description's example mirrors the schema examples and adds no new parameter semantics beyond demonstrating a call. Baseline 3 is appropriate.

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?

Description opens with a specific verb and resource: it returns parsed transaction history for a Solana address with a defined set of enriched fields. It distinguishes itself from a 'raw signature list' and from sibling asset-focused tools like helius_asset, so an agent can tell what it does.

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 makes the intended context clear: use this when you need human-readable, enriched transaction history (swaps, NFT sales, transfers) rather than raw signatures. It does not name explicit sibling alternatives or when-not-to-use conditions, but the examples and 'Deeper than a raw signature list' line give practical guidance.

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