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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: the per-call cost ($0.005 USDC via x402) and the endpoint, plus the shape of the returned fields. It does not explain what a free-trial call yields or how many calls are free, but the paid-call disclosure is a real value-add.

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, front-loaded with the resource and returned fields, then the limit constraint, then pricing. Nothing is wasted, though the raw pricing URL is slightly bulky for the information it carries.

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 read-only single-address query with no output schema, the description covers what is returned, the count constraint, and the payment model, which is enough for an agent to call it correctly. Only the free-trial/payment-requirement behavior is left entirely to the schema.

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 (base58), limit (1-50, default 10), and payment. The description only restates the limit range and default, adding no new semantics. Baseline 3 is appropriate when the schema does all the work.

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 and resource (most recent transaction signatures for a Solana address) and enumerates the returned fields (slot, time, success flag, memo). It implicitly separates itself from the singular sibling solana_transaction, but never names that sibling, so sibling differentiation is left to inference.

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?

Usage is only implied: an agent can infer this is the tool for recent activity on an address, and the limit default (10) hints at the common case. There is no explicit when-to-use vs when-not, and no mention of when solana_transaction or solana_account_info would be the better choice.

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