check_chain_status

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

No annotations, but description clearly states what the tool returns (health, liquidity, addresses, contracts, route config) and implies read-only behavior. No hidden side effects or contradictions.

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?

Front-loaded with purpose, then usage guidance, then bullet list. No redundant sentences. Efficient and well-structured.

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?

No output schema, but description covers what each parameter does and what the tool returns. Sufficient context for an agent to use it correctly alongside sibling tools.

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 coverage is 100%, baseline 3. Description adds meaning by explaining that destinationChainId optionally checks route configuration, exceeding schema's description.

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?

Description specifies checking chain health, solver liquidity, wallet addresses, depository contracts, and route configuration. Verb 'check' combined with specific resources distinguishes from sibling tools that only list chains or provide quotes.

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?

Explicitly states 'Use this before quoting to verify a route is viable' and lists checks. Provides conditional advice on health and liquidity. No explicit when-not, but strong contextual guidance.

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