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

Adds substantial context beyond the annotations: the output is unsigned transactions the wallet must sign, a USDG top-up approval is required when the position is under water, and the result includes closes_parts enumerating what is closed. This reconciles readOnlyHint with what otherwise sounds like a buy-back/return sequence, so the agent understands no state changes until signing.

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 the core action in the first clause, then the scope clarification. Two sentences with no filler, though the second is dense with domain jargon ("pair or basket legs", "closes_parts") that takes a careful read.

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 only two required params, high schema coverage, and no output schema, the description covers what the tool returns (unsigned txs, closes_parts) and the one prerequisite that could surprise an agent (USDG top-up approval). Nothing critical is missing, though it doesn't mention signing/gas flow beyond "for it to sign".

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% and both parameters are documented inline (ticker format, wallet address for signing). The description adds no further parameter syntax or format detail, so the 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?

States a specific verb and resource: produce unsigned transactions that close the wallet's entire short on a stock. It explicitly scopes to the whole short ("closes all of it") and names how that differs from close_pair, so an agent can separate it from siblings without opening schemas.

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?

Clearly routes between this tool and close_pair ("close_pair closes only a pair's own part"), and explains the shared-short-per-stock model that makes the choice non-obvious. It does not cover other adjacent alternatives such as buy_cover or repay, so it stops short of full when/when-not coverage.

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