fetch_price_feed_txn

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

With no annotations, the description carries full burden. It discloses that it builds unsigned transactions, calls fetch_price_feed(uint64) on the pool contract, and returns base64-encoded transactions for signing. This clarifies that the tool does not execute transactions itself, which is essential behavior.

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 only two sentences, front-loads the purpose, and includes the key behavioral details without any fluff. Every sentence earns its place.

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, the description adequately explains the return value (base64-encoded transactions) and the underlying operation. It omits any mention of error handling or how to use the signed transactions, but is sufficient for a simple transaction builder with 100% schema coverage.

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 description coverage is 100%, so each parameter already has a description in the schema. The tool description adds no additional parameter-level semantics beyond the contract call context, keeping it at the baseline.

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 it builds unsigned transactions to fetch the latest oracle price for a DorkFi lending market, specifies the contract function called, and distinguishes itself from sibling read-only getters and other transaction builders.

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 provides clear context that this is for building transactions rather than directly querying price, and notes the output is for signing. However, it does not explicitly mention alternatives like get_market or when not to use this tool, so it lacks full exclusions.

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