1s_network_info

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

No annotations are provided, but the description discloses that returned values are hex-encoded and gas price is in wei. This goes beyond simple purpose. However, it does not mention that the tool is read-only (implied) or provide details on error behavior.

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 only two sentences, with no redundant information. It front-loads the core purpose and adds usage guidance and format details efficiently.

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 no output schema, the description adequately covers the return values and their encoding. It lacks an explicit structure (e.g., JSON keys) but is sufficient for an agent to understand what to expect. The tool's simplicity (1 optional param) means less risk of incompleteness.

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 100% with enum and description for the 'network' parameter. The description adds context by specifying the outputs (chain ID, block number, gas price), which helps the agent understand what values are returned for a given input.

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 verb 'Get' and resource 'basic network information' with specific outputs (chain ID, latest block number, current gas price). This distinguishes it from siblings like 1s_chain_id which only returns chain ID.

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 explicit use cases: 'verify which chain you are connected to' and 'check current gas conditions'. However, it does not mention when to use alternative tools (e.g., 1s_chain_id for just chain ID), leaving some room for ambiguity.

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