estimate_moolah_energy

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by disclosing that results are 'historical typical values' and that on-chain simulation is not wired, which are important limitations not present in 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?

The description is compact and front-loaded with the main purpose. It efficiently conveys key information without unnecessary words, though it could be slightly more streamlined.

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?

With no output schema, the description does not detail return values but acknowledges they are historical typical values. For 4 parameters and no nested objects, the description provides sufficient context for a typical estimation tool, though more precision on output format would help.

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 coverage is 100%, but the description adds context for isTRX (explaining when to set true) and enumerates all valid operation values. This additional guidance goes beyond the schema descriptions.

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 estimates energy, bandwidth, and TRX cost for Moolah write operations. It specifies the domain (JustLend V2/Moolah) and distinguishes from sibling execution tools like moolah_borrow or other estimation tools like estimate_lending_energy.

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 instructs when to set isTRX=true and notes that estimation should happen before executing. It lists all covered operations. However, it does not explicitly exclude other protocols or provide guidance on when not to use this tool vs. estimate_lending_energy.

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