read contract

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds two useful behavioral facts beyond that: proxy contracts are supported and no wallet signing is required. It omits revert handling, whether results are decoded per the ABI, and gas/call constraints.

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?

Two short sentences with no filler, and the core capability is front-loaded before the no-signing note. Nothing is repeated from the title or schema.

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 five-parameter tool with zero schema description coverage and no output schema, the description says nothing about the return value shape (raw vs. ABI-decoded), error behavior on revert, or the ABI input format. Those are material gaps for an agent constructing the call correctly.

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 description coverage is 0% across five parameters, so the description must compensate and it does not. Key ambiguities remain unexplained: whether abi expects human-readable signatures or a JSON ABI array, that args must be positionally ordered to match functionName, and what blockNumber controls (historical state reads).

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 gives a specific verb and resource: it calls an ABI-described view or pure method on an arbitrary contract. It also notes proxy support and that no signing occurs, which frames it as a read-only call. It does not explicitly differentiate itself from the sibling contract_inspect, which likely also targets contracts.

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?

Usable context is implied: use this to read contract state via a view/pure function. However, there is no explicit when-to-use guidance, no mention of when NOT to use it (e.g., for state-changing calls, which this cannot do), and no routing to alternatives such as contract_inspect or decode_event_logs.

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