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

With no annotations, the description carries the full burden. It discloses the key behavior that no broadcast occurs, which implies no on-chain state change, but it omits other important behavioral details such as whether a recent blockhash is required, what the return value looks like, and how simulation failures are reported.

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?

A single sentence with no filler. The core action and the key distinction from broadcasting are front-loaded, and every word earns its place.

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?

Despite a simple two-parameter schema, the tool simulates transaction execution, which is conceptually complex. The description does not mention return values, error semantics, or prerequisites like a valid blockhash. With no output schema or annotations, this leaves an agent without enough context to invoke it confidently.

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 only 50%, and the description adds nothing about parameters. The transaction parameter is well described in the schema, but the network parameter is left as a bare enum without explanation of how it selects the cluster. The description fails to compensate for this gap.

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 'simulate' and resource 'Solana transaction', with the critical qualifier 'without broadcasting it' that distinguishes it from sending or broadcasting tools. It clearly separates from sibling getter tools like get_solana_balance and get_recent_transactions.

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 phrase 'without broadcasting it' implies the intended use case of a dry-run before sending, but there is no explicit when-to-use or when-not-to-use guidance. No alternatives are named, though none of the sibling tools perform a similar function.

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