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

No annotations are provided, so the description carries the burden. It discloses that the tool returns formatted balances with raw values, which gives some behavioral context. However, it does not explicitly state read-only behavior, error handling, or any side effects. The verb 'get' implies a read operation, but deeper transparency is lacking.

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, front-loaded sentence that state the purpose, lists tokens, and notes output format. No redundant words, and every element earns its place.

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 one required parameter and no output schema, the description adequately explains the input (wallet address), the scope (MegaETH tokens), and output (formatted balances with raw values). It lacks details like error conditions or network, but for a simple getter, this is largely complete.

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% for the address parameter, so the schema already documents it. The description adds a wallet context but does not add any new parameter semantics beyond what the schema provides. Baseline of 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 clearly states the tool gets all MegaETH token balances for a wallet, listing specific tokens (ETH, WETH, $MEGACHAD, USDm). This is a specific verb+resource pairing that distinguishes it from sibling tools like get_wallet_info or get_megachad_stats.

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 context: use when you need MegaETH token balances for a wallet. However, it does not explicitly mention alternatives or when not to use this tool, leaving the agent to infer based on tool names rather than receiving direct guidance.

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