Simulate a leveraged LP payoff curve

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

It adds meaningful behavioral detail beyond annotations by explaining the quote/base debt treatment. The readOnly and idempotent annotations are consistent and the description clarifies a non-obvious simulation assumption.

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?

Two concise, front-loaded sentences. No redundancy with the title/schema, and the key behavioral distinction about quote vs base debt is included economically.

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?

The description lacks essential context for correct use: no output shape, no guidance on how terminalPrices are interpreted, no constraints/edge cases. Given there is no output schema, this leaves significant ambiguity despite the clear core purpose.

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 description coverage is very low (~14%), and the description only clarifies the debt-asset behavior. It does not add meaning for depositUsd, leverage, lowerPrice, upperPrice, terminalPrices, or liquidationPrice beyond their parameter names.

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 uses a specific verb ('Project') and a specific resource (equity/ROE for a concentrated-liquidity position), which clearly conveys the tool's function. It does not distinguish from siblings, but no siblings are listed.

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 context is implied: use this when you need to model a leveraged LP position across terminal prices. However, there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives.

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