get_gas_price

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

No annotations are provided, so the description carries the burden. 'Current' usefully signals a live/fresh read with no historical parameter, which is the key behavioral trait here. However, it does not disclose return units (e.g. yoctoNEAR per gas), whether it hits the network or a cache, or any rate-limit behavior — gaps that matter for interpreting the result.

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?

A single front-loaded sentence with the resource immediately after the verb and zero filler. Every word earns its place and nothing essential is buried.

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-argument read tool the description is minimally sufficient, but with no output schema and no annotations, nothing anywhere tells an agent what the response looks like or in what unit the gas price is expressed. That single missing detail is the difference between adequate and complete for this tool.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly does not waste space inventing parameter detail.

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?

Clear verb+resource+scope: 'Get the current gas price on NEAR network' names both the action and the exact datum returned, and no sibling tool (block info, protocol config, account balance) overlaps with gas price retrieval. It does not explicitly contrast itself with siblings, but the resource is distinctive enough that an agent can select it unambiguously.

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?

Usage is only implied — an agent infers it should call this when a gas price is needed, but the description offers no explicit when-to-use statement, no mention of alternatives (e.g. protocol config may expose gas parameters), and no guidance on freshness or caching. The word 'current' hints at live retrieval but nothing more.

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