pendle_get_market_history

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

Since no annotations are provided, the description carries the full burden. It explains the tool is for historical data, lists available fields, and provides interpretation guidance. It does not explicitly state it is a read-only operation, but the context implies it.

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 informative but not overly verbose. It uses bullet-like listing for fields and provides context on interpretation. Could be slightly more structured with separate sections, but it is efficient.

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 explains the return data (time-series of metrics), provides interpretation guidance, and mentions the default period. It is complete enough for an agent to understand what the tool does and how to use it.

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 listing all available fields in text, explaining the default period, and clarifying that 'all' can be used for the fields parameter. This goes beyond just repeating schema descriptions.

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 returns 'historical time-series data for a Pendle market' with specific metrics. It distinguishes itself from sibling tools like pendle_get_market_details (current snapshot) and pendle_list_markets (find addresses).

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?

Explicitly tells when to use this tool ('trend analysis, yield stability assessment') and provides alternatives ('Use pendle_get_market_details for current market snapshot. Use pendle_list_markets to find market addresses.').

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