get_chain_info

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

With no annotations, the description carries the full burden of behavioral disclosure. It is a read-only operation by implication, but it does not disclose any specifics such as required network connection, potential latency, or what data fields are returned. No behavioral traits are revealed beyond the basic action.

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, short sentence, which is concise. However, it is under-specified: it omits essential detail about what 'information' is provided, making it less helpful than a concise but complete statement would be.

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 no output schema and no annotations, the description should clearly define what the tool returns. It does not mention the type of information, the response format, or any edge cases. A more complete description like 'Returns the chain ID, network name, and latest block number' would be far more suitable.

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?

There are zero parameters, and the schema description coverage is vacuously 100%. The baseline for 0 parameters is 4, and the description does not need to explain parameter semantics. It adds nothing beyond the schema, but that is acceptable since there is nothing to document.

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 says 'Get information about the connected blockchain' but does not specify what information it returns (e.g., chain ID, network name, block height). The verb+resource pattern is present, but the purpose is too vague to distinguish it from many sibling tools that also retrieve blockchain-related information.

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. It does not mention prerequisites, typical use cases, or exclusions, leaving the agent without context on when this should be called.

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