polygon_gas

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

Annotations are absent, so the description must disclose behavior. It does mention 'Pay-per-call ($0.005 USDC)' which is a cost disclosure. However, it does not clarify read-only nature, rate limits, or response format variations, though the core data returned is explicitly stated.

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 extremely concise, with one informational sentence and a cost detail. It is front-loaded with the core purpose, making it efficient to parse.

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?

The core output is clearly defined, but the undocumented 'fields' parameter creates a completeness gap. There is also no mention of how the price is derived or any limitations, though for a simple gas price tool this is partially acceptable.

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?

The single 'fields' parameter is entirely undocumented in both schema and description. With 0% schema coverage, the description should have explained acceptable values, but it does not mention this parameter at all.

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 returns current polygon gas price in gwei and wei, plus estimated cost for a 21k transfer. This is specific and distinguishes it from other polygon tools (e.g., health, block) by focusing on gas pricing.

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 provides no guidance on when to use this tool versus siblings like base_gas or polygon_health. It does not explicitly state it is for polygon network or any conditions for usage, leaving the agent to infer from the name.

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