dero_get_gas_estimate

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

Annotations indicate readOnlyHint=true; description adds 'This is a PRE-FLIGHT check; nothing is submitted.' and details output schema, adding context beyond annotations.

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?

Description is well-structured with front-loaded purpose, then usage guidelines, input requirements, and output. No wasted sentences; each sentence adds value.

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 complex gas estimation tool, description covers purpose, when to use, critical input constraints, parameter meanings, and output format. No output schema but description provides fields.

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?

Schema has 100% coverage but description adds critical constraint: 'At least ONE of transfers, sc, or sc_rpc MUST be provided.' Also explains sc and sc_rpc semantics beyond schema.

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?

Description clearly states 'Estimate gas (compute + storage) for transfers, SC deploys, or SC invokes' with specific verb and resource. Distinguishes from sibling tools by noting it's a pre-flight check.

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?

Explicitly says 'When to call: BEFORE any wallet-side transfer/scinvoke...' and 'PREFER citing dero_docs_search' for understanding, providing clear guidance on when to use this tool vs alternatives.

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