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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is established. The description adds 'their data comes back as it is' and 'Pass atBlock to call again', giving a hint of behavioral traits (data fidelity and re-call semantics) beyond the annotations. However, it doesn't disclose error handling, rate limits, or what happens with invalid inputs. This adds modest value but stays short of rich behavioral context.

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 verbose and includes promotional content: 'Singularity Agent's MCP server, a live seat on The Wall (hosted by them)' and a URL. The core functional sentence is present but buried among marketing fluff. It is not front-loaded; an agent must parse through irrelevant text to extract the actionable instructions. The inclusion of a link and brand messaging detracts from conciseness.

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?

With an empty schema and no output schema, the description is the only source of parameter and behavior context. It mentions abi, method, and atBlock but does not specify how to provide a contract address or chain identifier. It also fails to describe the return format or how success/errors are conveyed. Given the complexity of cross-chain reads and zero structured schema, the description is not complete enough for reliable agent invocation.

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?

Even though the input schema is empty (0 parameters defined), the baseline is 4 for zero parameters. The description explicitly names parameters: 'abi', 'method', and 'atBlock', and provides a semantic cue (human-readable form). This compensates for the lack of schema detail and gives an agent actionable clues on what to supply, though it doesn't specify formats or types fully.

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: 'Call a view function on an EVM contract (supply abi in human-readable form plus method), or read parsed account data on Solana.' This is a specific verb+resource pair with explicit scope across two chains. The name 'read_contract' combined with the description distinguishes it from siblings like balance or decode, which are also under the same provider but focus on different data.

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 via 'Read-shaped tools only (anything that buys, sells or writes refuses)' but does not explicitly contrast this tool with alternative read tools in the sibling set. It offers context that it is for reads and mentions capabilities, but lacks explicit 'when to use this vs that' guidance or prerequisites like needing an ABI or method. The guidance is inferred rather than directly stated.

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