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

Annotations already declare readOnlyHint=false, non-idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely new behavioral context the annotations cannot convey: the output is an unsigned transaction, CoinFactory never signs or sends it, and the paying wallet must be the creator itself. It does not say what happens if nothing has accrued or what format the returned transaction takes.

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?

Two short sentences, front-loaded with the artifact type and payload, then the sender constraint. No filler or repetition of the schema.

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 single-parameter transaction-building tool with no output schema, the description covers purpose, custody model, and signer constraint adequately. The main residual gap is the shape/encoding of the returned unsigned transaction and whether the claim can be re-run if it fails, which an agent building a signing flow would want.

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 would be 3, but the sentence "It pays the sender, so the creator wallet itself must send it" clarifies that wallet must be the creator/recipient rather than an arbitrary relayer — meaning beyond the schema's "Creator wallet that will send the claim".

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: an UNSIGNED transaction that pays a creator accumulated swap-fee ETH from RevenueManager. The 'UNSIGNED' framing distinguishes it from the read-side sibling get_creator_rewards and from the actual submission step, so the agent can tell what kind of artifact it produces.

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?

"It pays the sender, so the creator wallet itself must send it" gives a concrete precondition for correct use. It stops short of explicitly routing the agent (e.g. use get_creator_rewards first to check accrual, or that this only builds and does not submit), so it is clear context without full when/when-not guidance.

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