get_account_transfers

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states that the tool gets transfers from Solscan, but does not explain behavior such as how the 'limit', 'removeSpam', or 'excludeAmountZero' parameters affect results, nor mention pagination, rate limits, or response structure.

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 description is a single, front-loaded sentence with no filler. It is extremely concise and easy to parse, with the action and object stated immediately.

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 4 parameters, no annotations, and no output schema, the description is too sparse. It omits parameter semantics, pagination behavior, and guidance on when to use it relative to sibling tools. While the core purpose is stated, the description is not complete enough for an agent to invoke the tool with confidence.

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%, and the description does not explain any parameters. The parameter names like 'removeSpam' and 'excludeAmountZero' are somewhat self-explanatory, but the description adds no meaning beyond the bare schema, leaving exact behavior unclear.

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 the specific verb 'Get' with the resource 'SPL transfers of a Solana account' and names the source 'Solscan', clearly identifying the tool's function. It distinguishes from sibling tools like get_account_transactions or get_token_transfers by focusing on SPL transfers.

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 implies a use case for retrieving token transfer history, but it does not explicitly state when to prefer this tool over alternatives like get_account_transactions or get_token_transfers. No exclusions or conditional guidance are provided, leaving usage to be inferred.

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