get_gas_price_percentiles

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

Discloses that it uses standard eth_feeHistory and does not require mempool access, adding value beyond parameter names. No annotations are provided, so the description carries the burden well. Could mention that it returns a distribution but not the exact structure.

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 concise sentences plus a clean Args list. Front-loaded purpose, no wasted words, efficient structure.

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?

Covers main purpose, parameter details, and implementation context. Lacks explicit return value description but the purpose implies what to expect. Good given simplicity and lack of output schema.

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?

With 0% schema coverage, the description adds meaning for both parameters: lists specific chain values (polygon, arbritrum) and describes block_count with default and max. Slightly inconsistent with 'any supported chain', but still helpful.

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 it returns gas price distribution percentiles over the last N blocks, using a specific verb and resource. It distinguishes from sibling tools like swap checks and hello, which are unrelated.

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?

It mentions working on any supported chain and not requiring mempool access, providing context for when to use. However, it lacks explicit when-not or alternative tool comparisons.

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