get_moolah_market_history

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

Annotations already declare safe read-only behavior (readOnlyHint, idempotentHint, destructiveHint=false). The description adds value by specifying that it returns both current values (totalBorrow, totalCollateral, apy) and a list of historical points, offering behavioral detail 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 two sentences long, front-loading the main function and then detailing return structure and usage hint. Every sentence contributes meaning without redundancy.

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 (current data plus time series) and no output schema, the description explains the return structure adequately. However, it omits details about the fields within the historical points list, which might be needed for full completeness.

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 input schema covers both parameters (network, marketId) with descriptions, achieving 100% coverage. The description adds context by noting that marketId should come from get_moolah_markets, enhancing the schema's meaning.

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 explicitly states it returns a 'Time series of a V2 Moolah market's borrow/supply APY, utilization, and totals', clearly identifying the verb (get), resource (V2 Moolah market history), and distinguishing it from sibling tools like get_moolah_market (current snapshot) or get_moolah_markets (list of markets).

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 advises to 'Use marketId (bytes32 hex) from get_moolah_markets', guiding the user to first retrieve the marketId from a sibling tool. While it does not explicitly state when not to use this tool, it provides sufficient context for appropriate usage.

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