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

Annotations declare read-only/idempotent/non-destructive, and the description is consistent: the output is unsigned transactions for the wallet to sign, not a state change. It adds context the annotations cannot convey — prerequisite approvals, the lending-fee mechanic, and leverage ceilings — though it omits what happens on failure or whether quotes/prices are fetched at build time.

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?

Front-loaded with purpose in the first clause, followed by mechanism, then prerequisites and limits; no filler sentences. The first sentence is long and jargon-dense, which slows scanning slightly, but each 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?

With no output schema, the description correctly identifies the return as unsigned transactions and covers prerequisites and leverage limits. For a read-only transaction builder that is nearly complete; only failure modes and the source of the approval requirement ('if needed') are left implicit.

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 each of wallet/symbol/margin/leverage is already documented, which sets the baseline at 3. The description does add one useful constraint beyond the schema — the per-symbol maximum leverage — but says nothing extra about margin semantics or symbol validity beyond what the schema states.

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+resource: it returns unsigned transactions that open a leveraged long on a stock, and explains the concrete mechanism (USDG margin + flash-borrowed debt, stock lent and posted). That mechanism implicitly separates it from open_short/open_pair/close_long, though no sibling is named explicitly.

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?

Gives real sequencing guidance: approve the margin and authorize LeverRouter on Morpho if needed, then open. It also bounds applicability with per-symbol leverage caps (1.80x on SPY/QQQ/NVDA, 1.35x elsewhere). It never states when to choose this over open_pair or open_short, so it stops short of explicit alternatives.

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