pendle_get_portfolio

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

No annotations provided, so description carries full burden. It details the output: PT, YT, LP balances, USD valuations, maturity dates, APY, strategy inference, expiry warnings. However, it does not explicitly state that it is read-only, though 'View' implies no side effects.

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 concise with two main sentences, a bullet-like list of output fields, and three usage guidelines. It is front-loaded and every sentence provides 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?

Given the tool's simplicity (2 params, no output schema), the description adequately explains the output details and usage context. It covers balance types, valuations, dates, APY, and provides references to related tools.

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. Description adds minimal parameter meaning beyond schema, only repeating 'all chains or specific chain' which is already in the chain parameter description.

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 'View a wallet's Pendle positions' and specifies it can be across all chains or a specific chain. It distinguishes from siblings like spectra_get_portfolio and other Pendle tools, providing a specific verb-resource pair.

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 provides alternatives: 'Use pendle_get_market_details to drill into a specific market. Use mv_plan_rollover to plan rollovers. Use spectra_get_portfolio for Spectra positions.' It also states it is the Pendle equivalent of spectra_get_portfolio, guiding selection.

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