Stablecoin Yield & Carry Arbitrage Radar

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description adds useful scope context (which protocols and rate types are covered) but says nothing about data freshness, whether rates are live or cached, or how results are ranked/returned. With annotations carrying the behavioral load, this is adequate but not rich.

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?

One front-loaded sentence beginning with 'Use this tool when...' with zero filler, which is the right shape for a routing-style tool. It is a long, dense sentence with a multi-clause list, but every clause carries routing information, 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?

For a read-only analytic tool with one well-documented optional parameter and no output schema, the description covers the domain and the comparison intent but leaves unclear what the response actually contains — a ranked opportunity list, per-protocol spreads, or a single best route. Since there is no output schema, the description carries some burden for describing the shape of results and does not discharge it.

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?

The single 'leverage' parameter is fully documented in the schema (range 1-10, default 5) at 100% coverage. The description never mentions leverage at all, so it adds no meaning beyond the schema — but the schema baseline for a well-covered single param is a 3. Note the parameter suggests the tool prices a hypothetical loop position, which the description should ideally surface.

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 the concrete domain and the exact comparison it performs: stablecoin yield / leveraged carry, contrasting Ethena sUSDe and Sky sUSDS yields against cheapest USDC borrow rates on Morpho Blue, Fluid, and Euler V2. That implicitly distinguishes it from the sibling tools, which each simulate a single protocol, but it never explicitly says 'this is the cross-protocol aggregator versus the per-protocol simulators'. The action verb is also implied by 'radar' rather than stated outright.

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?

It gives three specific trigger intents ('where to find the best DeFi stablecoin yield', 'how to loop stablecoins for leveraged carry', 'compare sUSDe and sUSDS yields against cheapest USDC borrow rates'), which is strong positive routing guidance. It stops short of exclusions — nothing says when to prefer simulate_sky_susds_leveraged_carry or the other per-protocol siblings instead.

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