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

The description goes well beyond the annotations by disclosing that the tool returns an unsigned transaction, that the service never signs or holds keys, that the user must approve and send the transaction, and that the action is irreversible once mined. It also explains that re-enrolling replaces the previous binding. This gives the agent an accurate model of the side effects and user involvement required.

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?

Every sentence in the description carries essential information: purpose, role distinction, wallet funding rules, prerequisites, return format, and irreversibility. The text is dense but not bloated, and the most important purpose statement appears first.

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?

The description compensates for the lack of an output schema by explicitly stating the return shape ({chainId, to, data, value}) and the accompanying voucher. It also covers the signing workflow, the Entry pass requirement, wallet constraints, and the irreversible nature of the action. An agent has enough information to call this tool correctly and anticipate downstream steps.

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?

Although schema coverage is 100%, the description adds important semantic meaning to both parameters: 'player' is explicitly the Entry pass holder, and 'gameWallet' is the wallet whose trading gets scored. It also adds practical constraints (e.g., $5 USDC minimum, gas cap) that inform what values are appropriate to pass.

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?

The description uses a specific verb ('Register') with a concrete resource ('the wallet that will actually trade during the season') and immediately distinguishes the player address from the game wallet. It also clarifies that re-enrolling replaces a previous binding, which separates this from the sibling claim/check tools. The purpose is unmistakable even without reading 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?

The description clearly gives context for when to use the tool: an Entry pass is required, and the game wallet must be a fresh, properly funded wallet at the opening bell. It does not explicitly name sibling alternatives or when not to use this tool, but the prerequisites and wallet constraints effectively define the appropriate usage scenario.

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