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

No annotations provided, so description carries full burden. It discloses a cost dimension ('$0.001 USDC on Base via x402'), which is valuable non-obvious behavioral info beyond what schema shows. Doesn't mention rate limits, auth, or freshness/caching behavior, keeping it short of a 5.

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?

Two tight sentences: first states what/where, second gives use cases plus pricing. Every clause earns its place, front-loaded with the resource.

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 the description enumerates returned fields (chain tip, gas price, base fee, utilization), which fully compensates. Missing optional info like default network when param omitted, but overall sufficient to invoke correctly.

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?

Single enum param (network: base|ethereum) with 0% schema description coverage. The description names both supported networks, matching the enum, but adds no format or default semantics. Baseline for a 1-param enum tool with no description coverage is 3.

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?

Specific verb+resource: 'Get current gas conditions on Base or Ethereum' with concrete returned fields listed (chain tip, legacy gas price, base fee, gas utilization). Clearly distinct from siblings like chain-block-number or chain-transaction-status.

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?

Names concrete use cases (transaction timing, fee checks, pre-trade context, autonomous execution) but doesn't state when NOT to use it or name a specific sibling alternative. Still, the enumerated scenarios give clear context selection.

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