heliusChain

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

No annotations are provided, so the description bears full responsibility for behavioral transparency. It mentions a range of operations (e.g., 'simulateTransaction' implies a simulation, not a real mutation), but it does not disclose side effects, authentication needs, rate limits, or whether operations are read-only or state-changing. The lack of detail for a complex tool is a significant gap.

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 concise at two sentences, covering purpose and a usage hint. However, given the tool's complexity, the conciseness comes at the cost of omitted essential detail. Still, it is not verbose and gets the core idea across quickly.

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?

The description is far from complete for a tool with 24 parameters, many actions, no output schema, and no annotations. It does not explain the role of the 'action' parameter, parameter dependencies, or expected outputs. Sibling tools exist for more specific tasks, but this tool's scope is poorly delineated. The description needs to be expanded significantly.

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?

With only 13% schema description coverage, the description should compensate by explaining key parameters. However, the description provides zero information about parameters such as 'action', 'address', 'mint', 'slot', etc. It does not even mention that 'action' selects the operation. This is a critical omission for a tool with 24 parameters.

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 lists multiple capabilities ('Raw chain state, token accounts, stake reads, blocks, network status, priority fees, and transaction simulation') which gives a broad but clear sense of the tool's domain. It also explicitly states what not to use it for ('not wallet portfolio summaries'), distinguishing it from sibling heliusWallet tool. A more specific verb like 'read' or 'query' could improve clarity.

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 includes a negative guideline ('not wallet portfolio summaries') which helps avoid misuse, but it does not explicitly mention when to use alternative sibling tools (e.g., heliusTransaction for transactions, heliusAccount for account data). It gives some context but lacks comprehensive alternatives.

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