get_chain

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

The description only states 'Get the chain of the wallet' with no behavioral details. Annotation openWorldHint is vague and does not convey safety or side effects. No information is given about the return format or edge cases.

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 one short sentence, extremely concise with no wasted words. However, it may be too terse to convey necessary context, preventing a 5.

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 simple getter, the description is minimal but lacks any explanation of return values or behavior related to the chainId parameter. Without an output schema, the agent is left without essential information about what the tool returns.

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 fully documents the optional chainId parameter with a clear description. The tool description adds no additional parameter semantics, but schema coverage is high at 100%, so baseline 3 is appropriate.

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 uses the verb 'Get' with resource 'the chain of the wallet', clearly indicating it retrieves the wallet's chain. However, it does not differentiate from sibling tools like evm_get_chain_info or list_supported_chains, so not a full 5.

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?

No guidance is provided on when to use this tool versus alternatives. There are sibling tools such as evm_get_chain_info and list_supported_chains that could overlap, but no mention is made.

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