aries_oracle_price

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

No annotations provided, so description carries full burden. Discloses read operation, opcode, and return fields, but omits error behavior (e.g., if feed not found) or side effects. Adequate but not thorough.

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?

Four straightforward sentences front-load purpose and inputs. No redundancy, but could be more structured with bullet points for return fields.

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 no output schema and 4 parameters, description covers inputs, outputs, and setup requirements. References external doc for template, which is helpful. Slightly light on error conditions.

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 only 25%, but description explains block and tx as 'alkane id' and symbolId as 'Symbol id registered in the feed'. Adds meaning beyond raw 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?

Explicitly states 'Read the latest price' with specific resource (Chainlink-style Alkanes price-feed oracle) and opcode. Distinguishes from siblings like aries_oracle_read by focusing on price feeds.

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?

Clearly explains inputs (alkane id {block,tx} and symbolId) and prerequisites (deployed feed instance). Refers to external docs for template details. Lacks explicit when-not-to-use, but context is sufficient.

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