solana_forensics_execute

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

Discloses that large results are automatically paginated and that continue is needed for subsequent pages, adding useful behavioral context beyond annotations. However, it does not mention whether operations are read-only, any side effects, authentication requirements, or error behavior, which is important for a generic executor tool with no annotations.

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?

Highly concise and well-structured: purpose, prerequisite, argument explanation, and pagination are each addressed in separate sentences without redundancy. Every sentence serves a clear function.

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?

Given the generic nature of the tool, the description covers the essential workflow: get schema, execute, handle pagination. The presence of an output schema reduces the need to describe return values. It could improve by explicitly mentioning discover for listing operations, but the sibling tool names imply that.

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 coverage is 0%, so the description compensates partially by explaining the operation parameter as an identifier (with an example) and the params parameter as matching the schema. Yet it does not enumerate possible operations or provide details about the params structure beyond referencing the schema, leaving significant ambiguity.

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?

Clearly states it executes a Solana forensics operation with specified parameters, providing a concrete example operation identifier. It distinguishes itself from siblings by being the executor, while discover, get_schema, and continue serve auxiliary roles.

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?

Explicitly instructs to use solana_forensics_get_schema first to understand required parameters, and mentions solana_forensics_continue for pagination. However, it does not explicitly mention when not to use this tool or mention solana_forensics_discover for finding available operations.

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