get_gas_price

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds that it returns the 'current' price and includes 'priority fee', which is useful context. However, it does not disclose additional behavioral traits such as caching, latency, or response format, which is acceptable given the annotations but not exceptional.

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 a single, concise sentence that front-loads the verb and resource. It contains no filler or redundant information, and every word earns its place.

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 zero-parameter read-only tool with no output schema, the description is complete. It clearly states what data the tool returns, and the sibling tools provide enough context for differentiation. No additional explanation of return values or behavior is necessary.

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 tool has zero parameters, so the schema imposes no burden. The description adds semantic meaning by specifying what is retrieved (gas price and priority fee), which goes beyond the empty parameter list. Per the rubric, a baseline of 4 is appropriate for 0 parameters.

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 'Get current Pharos gas price and priority fee' uses a specific verb ('Get') and clearly identifies the resource (gas price and priority fee). It is distinct from sibling tools like get_block or get_balance, and the scope ('current') adds precision.

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 does not explicitly state when to use this tool versus alternatives like estimate_gas. The usage is implied by the name and description, but no exclusions or alternative suggestions are provided. The context signal of zero parameters makes it straightforward, but guidance is still implicit.

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