aries_oracle_read

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

With no annotations provided, the description carries the full burden. It correctly states the tool is a staticcall-safe view (read-only) and explains the decode parameter. However, it does not cover failure modes, rate limits, or authentication requirements.

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 concise with two sentences. The first states purpose and key inputs, the second explains decode. It is front-loaded but could benefit from breaking down complex decode info into a list or table.

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?

Given the tool's complexity (oracle reading with opcodes and decode), the description covers purpose, inputs, and decode format. It references external docs for opcode details. Without an output schema, it explains how to interpret execution.data via decode. No missing critical information.

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 description adds significant meaning beyond the schema, which has only 33% coverage. It clarifies the purpose of block/tx as the oracle's alkane id, details decode options (raw, u128, utf8, bool, price), and provides examples for opcode and inputs.

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 reads a value from an oracle contract via a staticcall-safe view (alkanes_simulate). The verb 'read' and resource 'oracle contract' are specific, but it does not explicitly differentiate from sibling tools like aries_oracle_price, leaving some ambiguity.

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 explains what inputs to provide (alkane id, opcode, inputs) and references external documentation for opcode details. However, it lacks guidance on when not to use this tool vs. alternatives, such as aries_oracle_price for price reads.

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