read_contract

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

The description repeats the readOnlyHint from annotations without adding any new behavioral context. It does not describe return behavior, error handling, ABI fetching behavior, or any side effects. Annotations already cover safety, but the description contributes no additional transparency.

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 a single concise sentence with no unnecessary words. It front-loads the core purpose effectively.

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?

Given the tool has five parameters, no output schema, and many sibling tools with overlapping functionality (multicall, fetch_contract_abi, get_contract), this one-line description is insufficient. It does not explain what the function returns, when to use it versus alternatives, or how it handles missing ABIs.

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 input schema descriptions cover all five parameters (abi, args, network, functionName, contractAddress) with useful details, so the baseline is 3. The tool description itself adds no parameter semantics beyond that.

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 identifies the tool as calling read-only functions on a smart contract. The 'read-only' qualifier distinguishes it from write_contract and deploy_contract, and it clearly specifies the resource (smart contract) and action (call functions).

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 does not mention that write operations should use write_contract, nor does it clarify when to use multicall or fetch_contract_abi. Lacks any contextual cues beyond the basic purpose.

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