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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description still adds genuine context: results are ordered newest-first, a cursor pages backwards, and data is sourced live from public Solana JSON-RPC via getSignaturesForAddress, which tells the agent about freshness and provenance.

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, zero waste: the returned payload is front-loaded, followed by the natural-language framing and the data source. Nothing is redundant.

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?

With no output schema, the description carries the burden of describing returns, and it does: it lists every returned field, the sort order, and the paging mechanism. Combined with 100% parameter coverage and full annotations, an agent has everything needed 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 wallet, limit, until, and before. The description only adds that the cursor pages 'further back,' which lightly reinforces the `before` parameter but adds no syntax or format detail beyond the schema.

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 verb+resource ('recent transaction history for a Solana address') and enumerates the returned fields (signature, slot, block time, success/failure, memo). It implicitly separates itself from siblings like solana_transaction (single tx) and solana_wallet_balance, though it never names an alternative explicitly.

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 framing question 'what has this Solana wallet done lately' implies the use case, but there is no when-to-use/when-not guidance and no pointer to related tools such as solana_transaction for a specific signature. Usage is implied rather than stated.

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