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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states that recent transaction signatures are fetched and gives no details about ordering, pagination, rate limits, error behavior, or that only signatures (not full transaction data) are returned.

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 one-sentence description is front-loaded and contains no filler words. It states the core purpose efficiently, though its brevity sacrifices important behavioral and usage context.

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 three parameters, no annotations, and no output schema, the description is too minimal. It omits guidance on 'limit', 'network', return formatting, ordering/pagination semantics, and when to use this tool over its siblings, leaving an agent under-informed.

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 only 33%, with only 'wallet' described. The description repeats the wallet concept without elaborating on the 'limit' or 'network' parameters, so it adds little beyond the schema and fails to compensate for the missing parameter documentation.

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 names the specific operation ('get recent transaction signatures') and the subject ('a wallet address'). It clearly distinguishes from sibling tools like get_solana_balance or simulate_solana_transaction because it targets transaction signatures, not balances or simulation.

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 provides no when-to-use guidance nor any mention of alternative tools. An agent must infer usage solely from the tool name and operation; there is no context about when this tool is preferable to siblings or how network/limit choices affect behavior.

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