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

With no annotations, the description must carry the full behavioral burden. It discloses payment requirements ('PAID $0.02 per call'), explains that a payment requirement is returned until a payment method is provided ('payment header, bundle_token, or api_key'), and mentions the API endpoint. This provides transparency about the tool's behavior without annotations.

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 concise (two sentences) and front-loaded with the price and URL, followed by the functional purpose and payment behavior. Every clause contributes useful information without redundancy.

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?

For a tool with no output schema and only three simple parameters, the description covers the essential context: what data is returned (gas price in gwei, verdict), the payment model, and the specific use case. It does not detail the exact response structure, but given the simplicity, this is sufficient.

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 0%, so the description must explain the parameters. It explicitly mentions all three parameters—`payment`, `bundle_token`, and `api_key`—and clarifies their role as authentication/payment mechanisms that bypass the payment requirement. This adds meaning beyond the bare schema.

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's purpose: 'Base (EVM) gas oracle: current gas price in gwei plus a submit-now / wait verdict for agents deciding when to broadcast a transaction.' This provides a specific resource (Base EVM gas) and the output (gas price + verdict), distinguishing it from all sibling tools, none of which are gas oracles.

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 intended use case is explicit: 'for agents deciding when to broadcast a transaction.' It also references get_free_api_key as a way to obtain a free-tier key, which guides the user on how to access the tool. However, it does not explicitly contrast with alternative tools, though no direct alternative exists among siblings.

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