pendle_list_expiring_markets

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

No annotations provided, so description carries full burden. Describes output grouping by urgency with clear thresholds (≤7d, ≤14d, ≤threshold). Does not explicitly state read-only behavior but implies it as a scanning tool. Lacks details on output structure (e.g., market addresses, maturity dates), but provides sufficient context for an agent to understand what this tool does.

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?

Front-loaded with main purpose and then provides urgency details, use cases, and alternatives. Well-structured but slightly verbose with the bullet-style urgency descriptions. Could be more concise, but each sentence adds value.

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?

Completeness is high given the tool's complexity and no output schema. Description covers purpose, urgency grouping, use cases, and alternatives. However, it does not explain the exact output fields or how the grouping is presented (e.g., categories as separate arrays), leaving some ambiguity.

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?

Parameter schema coverage is 100%, so baseline is 3. Description does not add any additional meaning to the parameters; it focuses on output grouping and use cases. The schema descriptions are already adequate for understanding each parameter.

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?

Description clearly states 'Scan Pendle chains for markets approaching maturity' and explicitly differentiates from sibling tool spectra_list_expiring_pools. The verb 'scan' and resource 'markets approaching maturity' are specific and distinct from other Pendle 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?

Provides explicit use cases for portfolio managers, curators, and traders. Lists three alternative tools with specific scenarios: pendle_get_market_details for full info, mv_plan_rollover for rollovers, and pendle_get_yield_curve for replacements. This gives clear guidance on when to use this tool vs alternatives.

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