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

Annotations already establish this is a non-read-only, non-destructive, idempotent, closed-world write operation. The description adds substantial behavioral context beyond that: it produces unsigned transactions and atomic EIP-5792 batch calls, operates on Base, and automatically supplies collateral into Aave V3 or Morpho to recover principal plus developer fee.

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 sentences, both front-loaded with the most important information: what is generated and the zero-net-cost mechanism. There is no filler or repeated content.

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 complexity, complete schema descriptions, and an output schema, the description is nearly complete: it covers chain, output type, and collateral recovery mechanics. It could be slightly stronger by stating preconditions or when to call it relative to quote/rate tools, but no critical invocation detail is missing.

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 100%, so the baseline is 3. The description adds meaning by explaining that collateral is automatically supplied via Aave V3 or Morpho, which clarifies the protocol and collateral parameters, though it does not add detail for buffer or amount beyond the schema text.

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 states a specific verb and resource: generate ready-to-sign EVM transactions and EIP-5792 atomic batch calls for a zero-net-cost payment. It also pins the domain to Base (Chain ID 8453), clearly separating this construction tool from read-only siblings like get_rates and get_quote.

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?

Usage is implied by the phrase 'for a zero-net-cost payment on Base,' but there is no explicit when-to-use guidance or routing relative to get_rates/get_quote. It does not state prerequisites such as needing a quote first, nor does it name exclusions.

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that this is a pure computation (a quote for a payment), which is useful but does not disclose anything about rate limits, freshness of the quote, or whether results expire.

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?

A single front-loaded sentence with no filler. It is somewhat list-heavy, but every clause maps to an actual computed output, so nothing is wasted.

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 output schema exists, so return values need not be re-explained, and annotations cover the safety profile; the description still enumerates the quote components, which helps an agent understand the response shape. The main gap is the missing relationship to build_payment/get_rates, but the core of what an agent needs to call it correctly is present.

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 100%: amount, buffer, protocol (with enum semantics), and collateral are all documented with examples and defaults in the schema. The description adds no parameter-level detail, so the baseline of 3 applies.

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?

States a specific verb (calculate) and precisely enumerates what is computed: collateral requirements, developer fee, yield deposit, and recovery days, scoped to a zero-net-cost USDC payment on Base. That output list makes it distinguishable from get_rates/build_payment in substance, but no sibling is named explicitly, so it falls short of 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?

No when-to-use guidance is given: the description never states that this is a pre-payment quote to run before build_payment, nor does it contrast with get_rates. Usage is only inferable from the phrase 'for a zero-net-cost USDC payment,' which is context, not instruction.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds only that data is real-time and aggregated across two protocols; freshness/caching behavior is left to the schema's refresh parameter rather than the description.

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 tight sentences, zero filler, with the resource, protocols, and chain front-loaded before the profitability note. Every clause carries information.

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?

An output schema exists, so return values need not be explained, and annotations cover safety; the description supplies protocol and chain scope plus the profitability signal. It could still note aggregation or update cadence, but nothing essential for correct invocation is missing.

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?

With a single parameter at 100% schema description coverage, the schema fully documents 'refresh' and its default. The description contributes only the generic notion of 'real-time' data, which loosely maps to the refresh semantics but adds no format or syntax detail beyond the schema.

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 names a specific verb and resource ('Get real-time supply APYs'), scopes it to concrete protocols and chain (Aave V3, Morpho, Base Mainnet), and is clearly distinct from the siblings get_quote and build_payment. An agent can identify the tool's domain without opening the schema.

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?

Usage is only implied: 'the most profitable protocol for capital recovery' suggests when the tool is useful, but there is no explicit when-to-use/when-not guidance and no routing against get_quote or build_payment, which an agent may need to disambiguate rate-checking from quoting.

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