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

Goes beyond the annotations by stating the return contract (next unsigned transaction plus a review link) and that the tool 'never signs', which tells the agent a signing step is still required downstream. It does not state prerequisites, gas implications, or whether the collection is atomic across the listed asset types.

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 for the purpose followed by a short clause on the return contract. No filler, and the what-gets-collected list is front-loaded.

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 carries the return-value burden by naming the unsigned transaction and review link. For a non-idempotent, open-world mutation it could still say more about prerequisites or partial-failure behavior.

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?

Only one parameter and schema description coverage is 100%, with the schema already explaining that 'wallet' is the signing wallet. The description adds nothing about the parameter, 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 (prepare) plus the resource (a collect operation) and enumerates exactly what is swept up: USDG and lend assets from loans, collateral back, vault earnings and sGAGE rewards. It does not, however, distinguish itself from the sibling gage_prepare_reclaim, which plausibly overlaps with 'collateral back'.

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?

The phrase 'everything ready' implies the trigger condition (use this when positions are collectible), but there is no explicit when-to-use guidance and no alternative tool is named. The overlap with gage_prepare_reclaim is left entirely unresolved.

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