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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does convey that the tool performs RPC verification and optionally adds Blockscout enrichment ('when available'), which are useful behavioral traits. However, it does not mention potential failure modes, rate limits, or what happens for invalid addresses, which would be expected for a tool with no annotation safety hints. It is not misleading but lacks depth.

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 and front-loaded with the primary purpose. The second sentence packs a lot of detail efficiently without excessive wordiness. It is well-structured, though the second sentence is long and could be split for readability; still, it remains concise and scannable.

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 an output schema (not shown) and high schema coverage, the description provides a solid overview of the tool's behavior and output categories. It covers both chain families and the enrichment condition, which is sufficient for an agent to decide whether to call it. It does not address edge cases like invalid addresses or unsupported chains, but the schema already constrains the chain values, and the output schema presumably defines the return structure. The description is complete enough given the available structured data.

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?

The schema covers both parameters at 100%, so the description's contribution is limited. It does add meaning by clarifying that the chain parameter splits into two families (Solana/Slonana vs EVM) and that the address format differs accordingly, which reinforces the schema. However, it does not provide examples or further syntax details beyond the schema, so it meets the baseline for high coverage without exceeding it.

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 opens with a clear, specific verb ('Introspect') and resource ('program/contract address'), and immediately distinguishes two execution paths (Solana/Slonana vs EVM) with concrete facts returned for each. This makes the tool's function unmistakable and separates it from siblings like discover_programs, which targets discovery rather than introspection.

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 when to use the tool: when you have a specific address and want verified facts about it. However, it does not explicitly state when not to use it or name alternative tools such as solana_getAccountInfo or evm_rpc, which could also handle raw account/RPC introspection. The guidance is implicit rather than explicit, so it falls short of a 4.

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