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

readOnlyHint=true is already supplied by annotations, but the description usefully adds that this only *prepares* a call (no execution) and that the proceeds are rebasing stETH returned to the sender. It omits approval/permit requirements and any precondition checks, which matter for a transactional preparation 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?

A single dense sentence with the action front-loaded and no filler. It is efficient, though so terse that it sacrifices any routing or prerequisite structure.

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 annotations on safety, a full output schema, and complete parameter documentation, the remaining gap is routing: among many Lido-related siblings (prepare_lido_wrap, prepare_wrap_unwrap, prepare_lido_withdrawal_request/claim) the agent gets no explicit decision rule. Adequate but not fully self-sufficient for selection.

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%, so the baseline is 3. The only added nuance is "exact share amount" in the description, which reinforces the share-denominated (non-rebasing) nature of `amount` beyond the schema's "base units" wording; chain_id's Ethereum-1 restriction is left to 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?

"Prepare a direct wstETH unwrap call" gives a specific verb plus resource, and the qualifiers "direct" and "rebasing stETH" separate it from the queued withdrawal path (prepare_lido_withdrawal_request). It stops short of naming the sibling it displaces (prepare_wrap_unwrap, prepare_lido_wrap), so the differentiation is inferential rather than explicit.

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 "direct ... unwrap": an agent can infer this is the synchronous share-to-stETH path rather than the withdrawal queue. There is no explicit when-to-use, when-not-to-use, or named alternative, and no prerequisites such as needing wstETH balance or an approval.

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