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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value beyond them: the upstream source (public Mantle RPC), the explicit scope exclusions (treasury AUM and per-blob EigenDA stats not reported), and a pricing model ($0.002 per successful call via x402, failed calls not charged).

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 definition is front-loaded with the resource and data source, then enumerates returned fields, exclusions, and pricing. The field enumeration is dense but each clause conveys distinct content, so waste is minimal; it is slightly long but earns its length.

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?

An output schema exists, so return values needn't be re-explained, yet the description comprehensively states what is and isn't in scope, the data source, cost, and payment mechanism. Nothing an agent needs to call it correctly is missing.

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?

Parameter count is zero, so there is nothing parameter-specific to document; baseline is 4. No syntax or format details are needed and none are missing.

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 states a specific verb and resource: Mantle Network L2 telemetry from the public Mantle RPC, and enumerates exactly which blocks and metrics are returned (latest/safe/finalized, lags, gas price, base fee, gas used %, average block time). This is unmistakably distinct from sibling RPC/L2 tools like crypto_ethereum_gas_telemetry or crypto_arbiscan_l2_rollup, which target other chains.

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?

Usage is implied by the detailed list of returned fields, and the description usefully scopes out what is NOT available (treasury AUM, per-blob EigenDA stats). However, there is no explicit when-to-use guidance or named alternative the agent should prefer for adjacent queries.

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