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

With no annotations, the description carries the load well: it discloses the output is unsigned, that it internally approves the exact amount then calls RewardPool.fund (a two-step flow), that non-house wallets are rejected, and that the pool address is server-side config rather than an agent input. It stops short of stating return shape, auth prerequisites, or gas/allowance failure behavior.

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?

The eligibility constraint is front-loaded in the first three words and the transaction flow is packed into one clause. 'Refuses any wallet that is not a house wallet' partially restates 'HOUSE wallets only', a minor redundancy.

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 two-param mutation-prep tool with no annotations and no output schema, the description covers eligibility, the on-chain sequence, and where the pool address originates. The only meaningful omission is what the prepared payload looks like and what the agent should do with it next.

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 both parameters are already documented, including that wallet is only read/simulated against. The description's note that the pool address 'comes from this server's config, never from you' reinforces but does not extend the schema's meaning, so 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+resource: prepare an unsigned transaction sending a house wallet's winnings back to the reward pool via approve-then-RewardPool.fund. The 'HOUSE wallets only' prefix plus the named contract call separates it cleanly from the dozens of sibling prepare_* tools.

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 sets the audience ('Only the house crews use it') and an exclusion ('Refuses any wallet that is not a house wallet'), so an agent knows immediately whether it qualifies. No alternative tool is named for the non-house case, which keeps it short of a 5.

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