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

Annotations only give readOnlyHint and openWorldHint, so the description carries the real burden and does well: it discloses the exact amount (10,000 tUSDC), that it has no cash value, that the recipient is the sending wallet, and crucially that it returns an unsigned transaction rather than performing a mint. It does not say whether the mint is rate-limited or one-per-wallet.

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 front-loaded sentence with no wasted words; the key fact (unsigned transaction) comes first and the qualifiers are parenthetical.

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 zero-param, no-output-schema tool the description covers what is produced (an unsigned tx), the amount, and the recipient. It could note that the caller must sign and submit the transaction and any per-wallet limit, but nothing essential is missing.

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?

The tool takes zero parameters and the schema defines no properties, so there is nothing for the description to clarify. Baseline of 4 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: 'Builds the unsigned transaction that mints 10,000 tUSDC'. It is clearly distinguishable from the sibling request_test_eth (different asset) without naming it explicitly, which keeps it short of a 5.

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 only implied – 'this week's test collateral' signals a testing/faucet context, but the description never says when to call this versus request_test_eth or what prerequisites apply. No exclusions or alternatives are named.

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