pendle_simulate_trade

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

The description clearly states the tool is 'purely informational' and does not execute any transaction, which is the key behavioral trait. However, it does not mention any potential side effects, authorization requirements, or error conditions. Given no annotations, it carries the full burden but covers the essential non-execution nature.

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 succinct and well-structured: a main sentence, bullet points of outputs, a clear negative statement, a sibling equivalence, and usage pointers. No redundant information; every sentence earns its place.

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 5 required parameters, no output schema, and the domain complexity, the description provides a good overview of the tool's functionality and outputs. It explains what the simulation returns but could benefit from more detail on the return format. Still, it is largely complete for agent decision-making.

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%, but the description enhances semantic understanding for the 'amount' parameter (context-dependent: underlying/SY for buy, PT for sell) and the 'side' parameter (buys vs sells PT). This adds value beyond the schema's basic 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 specifies the tool simulates a Pendle PT trade and its effect on a wallet's portfolio. It lists specific outputs (before/after comparison, positions, APY, concentration) and distinguishes from the sibling pendle_quote_trade and pendle_get_portfolio. The mention of being the Pendle equivalent of spectra_simulate_trade further clarifies its role.

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 explicitly states when to use (simulate trade impact) and what not to do (does not execute any transaction). It provides clear alternatives: use pendle_quote_trade for a detailed quote and pendle_get_portfolio for the full portfolio. This gives unambiguous guidance.

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