calculate_compound_yield

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

No annotations are present, so the description carries the behavioral disclosure burden. It does add two useful behavioral facts: the calculation is deterministic, and the tool costs 0.015 USDC on Base L2. However, it does not explain the return format, failure modes, or how the micropayment/settlement flow works, which is significant for a paid tool.

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 a single front-loaded sentence followed by a brief cost parenthetical, with no filler. The enumerated output list is slightly long, but it earns its place by specifying the tool's scope.

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?

There is no output schema, yet the description never states what the tool returns, such as schedule objects, interest curves, or matrix structures. It also does not specify the required payload shape, leaving an agent guessing about inputs and results for a paid, moderately complex calculation tool.

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 payload is only described as a generic JSON string and paymentSignature as a settlement signature. The description adds no parameter-level meaning, such as which fields the payload should include or how inputs map to APY/APR, compounding, or impermanent loss outputs, so it stays at the schema-coverage baseline.

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 ('Calculates') and names concrete outputs: deterministic DeFi APY/APR schedules, continuous compounding interest curves, and impermanent loss risk matrices. It is clear about what the tool produces, but it does not distinguish itself from closely named siblings like calculate_impermanent_loss or calculate_staking_apr_decay, so it does not earn a 5.

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 intended use is implied by listing APY/APR, compounding, and impermanent loss calculations, but there is no explicit when-to-use or when-not-to-use guidance. It never names alternatives such as calculate_impermanent_loss or calculate_staking_apr_decay, leaving selection between overlapping tools to inference.

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