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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds real behavioral context beyond them: the approval prerequisite, the gasless metaTx bypass, and that the call returns unsigned transaction data. It does not discuss failure/revert conditions or what happens to treasury state, so not a full 5.

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?

Three sentences, zero waste, front-loaded with purpose then prerequisites then return value. Dense tool references (approve_exchange_token, sign_receive_with_*) are necessary for chaining rather than filler.

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 6-param destructive write with no output schema, the description covers purpose, prerequisites, alternate execution paths, and the return shape. Minor gaps remain around error/revert behavior and whether the returned unsigned tx must be relayed via send_signed_transaction in direct mode.

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 every parameter (including tokenAddress's address(0) convention and executionMode's enum) is already documented in the schema. The description restates the approval/metaTx dependency for amount but adds no syntax or format detail beyond what the schema provides — baseline 3.

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 (deposits ERC-20 or native tokens into an entity's protocol treasury) and immediately names the concrete use case (seller deposit). An agent can distinguish it from sibling withdraw_funds and from the approve/transfer helpers without opening the schema.

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?

Explicitly routes prerequisites: 'For ERC-20, call approve_exchange_token first,' and gives the alternate path — skip approval in metaTx mode by passing transferAuthorizations to send_meta_transaction. This names the sibling tools and the condition that selects each path.

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