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

The description implies 'reads' suggesting a read-only operation, but it does not explicitly state that the tool has no side effects or mutations. There is no mention of authentication requirements, rate limits beyond the trial, or any potential costs or data usage implications. Without annotations, this level of transparency is insufficient.

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 succinct and free of redundant wording. It front-loads the core purpose ('Multi-chain onchain reads') and then includes a relevant note about trial limits. The structure is clean, and no unnecessary details are present, making it highly concise.

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 too generic to provide complete context for an agent. It does not specify the types of on-chain data that can be read, the supported chains or networks, or the output format. Without an output schema or further details, an agent cannot confidently determine when or how to use this tool for specific requests.

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 already defines 'chain' and 'network' with brief descriptions ('Chain to process', 'Network to process'). The tool description adds no extra meaning about these parameters, such as expected values, formats, or examples. Since the description provides no additional semantic value beyond the schema, the parameter semantics are minimal.

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 states 'Multi-chain onchain reads', which indicates the tool performs read operations across multiple blockchains. However, it lacks a specific verb (e.g., 'get', 'fetch') and does not clarify what kind of on-chain data is read (e.g., balances, transactions, contract state). The purpose is somewhat clear but under-specified.

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 provides no guidance on when to use this tool versus alternatives. It only mentions a trial limit ('5 free trial calls per signed wallet'), which is a restriction, not a usage scenario. No prerequisites, conditions, or alternative tool references are given, leaving the agent without direction.

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