sui_get_gas_price

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states what is fetched. It does not clarify that this is a read-only operation, what units the price is returned in (e.g., MIST), or any other behavioral traits like caching or network dependence. The concept of 'reference gas price' is not explained, leaving ambiguity.

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 is front-loaded with the action and resource. Every word is purposeful, with no unnecessary filler. It is maximally efficient for the tool's simplicity.

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?

While the tool is simple with no parameters and no output schema, the description does not mention the return format, units, or how the reference gas price is defined. This is a gap since the output schema is absent, so the agent must infer the response structure. The description is adequate but not fully complete.

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, and the schema is empty with 100% coverage. The baseline for 0 params is 4, and the description adds no confusing parameter details. The tool's simplicity means no parameter elaboration is needed.

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 specifies the verb 'Get' and the resource 'current reference gas price', making it evident that this tool fetches Sui's reference gas price. It distinguishes itself from sibling gas price tools like near_get_gas_price and get_gas_prices_all_chains by being specific to Sui, even without explicitly stating 'Sui'.

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 alternatives such as estimate_gas or get_gas_prices_all_chains. It does not mention any context, prerequisites, or excluded scenarios, leaving the agent without clear selection criteria.

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