logicnodes_gas_oracle

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

With no annotations, the description carries the full burden. It discloses the cost per call and real-time nature, which are important behavioral traits. However, it does not explicitly state that the tool is read-only or safe, but the nature of an oracle implies no destructive side effects.

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: two sentences and a cost line. Every sentence adds value with no redundancy or fluff. The most important information (purpose, outputs) comes first.

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?

Given the tool's simplicity (one optional parameter, no output schema, no annotations), the description provides complete context: what data it returns, which network, and the cost. The agent has sufficient information to decide and invoke.

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 input schema has 100% coverage as the sole parameter 'percentile' is fully described. The tool description adds no additional meaning beyond the schema, so the baseline score of 3 applies.

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 is a real-time gas price oracle for Base mainnet, listing specific return values (base fee, priority fee, EIP-1559 deviation). It distinguishes itself from sibling tools like logicnodes_sig_verify and logicnodes_peg_monitor, which serve different purposes.

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 implicitly suggests using the tool when needing gas price data, but provides no explicit guidance on when to use it over alternatives or when not to use it. The mention of cost and real-time data gives some context, but lacks direct usage instructions.

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