dero_get_encrypted_balance

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

Annotations (readOnlyHint=true) are consistent. The description adds critical behavioral context: the output is an opaque encrypted blob, only decryptable by the spend key holder. It explains the non-cleartext nature and the requirement for wallet control, which goes 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?

The description is well-organized with clear sections: intro, critical warning, usage guidance, input requirements, and output structure. Every sentence adds value and is front-loaded with the most important information.

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?

Despite no output schema, the description provides output field names (status, registration, balance). It covers all essential aspects: what the tool returns, constraints, and safety warnings. The complexity is adequately addressed.

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?

With 100% schema coverage, the description still adds value by clarifying address prefix (dero1/deto1), topoheight semantics (-1 for latest), and scid optionality. These details are not present in the schema descriptions, making parameter usage clearer.

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 retrieves an encrypted balance blob using DERO.GetEncryptedBalance. It distinguishes from sibling tools by specifying the unique output type (encrypted blob) and scope (address at a given topoheight), making the purpose unambiguous.

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?

Explicit guidance on when to call: for verifying on-chain encrypted state before transfers, or as a sub-step. It also recommends citing dero_docs_search for user education, and warns against presenting encrypted bytes as balance. This provides clear context and alternatives.

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