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

With no annotations provided, the description carries the full burden. It discloses what is returned per chain type: for Solana/Slonana (executable, owner, data size, known program) and for EVM (RPC-verified facts including ERC-20 and EIP-1967 proxy, plus Blockscout enrichment). It does not explicitly state read-only, but 'Introspect' strongly implies a non-mutating operation.

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 two sentences: the first immediately states the tool's core purpose, and the second efficiently details chain-specific return values. No unnecessary words or repetition; it is front-loaded and structured clearly.

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 multi-chain introspection tool, the description adequately covers key behavioral details and return values for both Solana and EVM, and notes the Blockscout enrichment. Given that an output schema exists (as indicated), the description does not need to enumerate every return field. It lacks explicit error behavior, but that is not critical for a read-only introspection tool.

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 100% for both parameters, and the schema already provides formats for chain and address. The description adds some mapping between chain names and address types (base58 vs 0x), but this is marginal beyond the schema. It does not significantly enhance parameter semantics.

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 clearly states the tool's function: 'Introspect ANY specific program/contract address on a chain.' It specifies the resource (program/contract address), the verb (introspect), and distinguishes from sibling tools like solana_getAccountInfo or evm_rpc by offering a higher-level, cross-chain introspection with chain-specific outputs.

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 usage for any specific address across multiple chains, and the chain-specific details indicate when each format applies. However, it does not explicitly name alternatives or exclusions (e.g., 'use discover_programs to list programs'), but the 'ANY specific' phrasing gives clear context that this is for a known, single address.

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