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

Annotations already declare readOnlyHint=true, so the description's job is to add risk context, and it does: disabling collateral can lower health factor or revert when open debt depends on it, and simulation is required. It doesn't say what the preparation produces (a plan/simulation result versus signable calldata), though an output schema exists to cover that.

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, no filler, and the action is front-loaded ahead of the risk caveat. Every clause carries information an agent needs before calling.

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 four-parameter, fully documented tool with an output schema, the description covers purpose, risk, and a hard simulation prerequisite. Remaining gaps are minor: no explicit sibling routing and no mention of what the prepared artifact is used for next.

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 all four parameters are already documented, including the 'fixed major-reserve list' constraint on asset and the boolean semantics of use_as_collateral. The description adds no format, default, or edge-case meaning beyond the schema, so baseline 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?

The description names the exact contract method (setUserUseReserveAsCollateral) and the resource (a supported fixed reserve), which distinguishes it from sibling Aave prepare tools like prepare_aave_v3_supply or prepare_aave_v3_borrow. It stops short of explicitly contrasting those siblings, but the verb+resource pair is specific enough to route correctly.

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?

Use is implied: toggle collateral on a reserve from the fixed major-reserve list. The description adds a real precondition ('exact wallet simulation is mandatory') but never states when to choose this over the other prepare_aave_v3_* tools or when not to attempt it (e.g., reserve unsupported, no position).

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