morpho_get_rate

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

Without annotations, the description effectively discloses that rates are live, dynamic, and can change unpredictably. It explains the return values (borrow APY, supply APY, utilization, liquidity) and implies a read-only operation. However, it does not cover error handling or requirements like authentication, slightly reducing transparency.

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 structured into three concise paragraphs, each serving a purpose: main action, behavior note, and integration advice. It is front-loaded with the core functionality, and no superfluous sentences are present. Slightly longer than minimal but justified.

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 fully explains the return data (borrow APY, supply APY, utilization, liquidity) and its purpose in looping strategies. It also provides pre-requisites (morpho_list_markets) and post-steps (spectra_get_looping_strategy), making it self-contained for the intended use case.

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%, so baseline is 3. The description adds value by explaining the market_key is a hex ID to be obtained from morpho_list_markets and by describing the output fields, which are not in the schema. This goes beyond simple repetition.

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 gets the borrow rate and market state for a specific Morpho market, distinguishing it from sibling tools like morpho_list_markets and morpho_get_positions. It also explicitly guides users on prerequisites and related tools.

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 explicit when-to-use guidance: for retrieving rates for looping profitability. It instructs users to first use morpho_list_markets to discover market keys, warns about rate volatility, and directs to spectra_get_looping_strategy for projections, offering clear alternatives and context.

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