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

With no annotations, the description carries the behavioral burden. It usefully discloses that the claim is 'unsigned,' implying no transaction is submitted, and it distinguishes the refund branch via raceId. It does not explain the signing/submission workflow, permissions, or other prerequisites beyond what the schema already says about wallet use and simulation.

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 description is a single compact sentence with the key Night Run context front-loaded and both modes expressed without wasted text.

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 low-complexity, two-parameter prepare tool with no output schema and no annotations, the description covers the core operation, the unsigned nature, and the refund variant. It could be slightly richer about the prepare/sign flow, but it gives enough to call the tool correctly.

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 the schema already defines both parameters and the raceId condition. The description reinforces the raceId/refund semantics and the default claim mode, but adds little beyond the structured parameter documentation.

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 states a specific operation: preparing an unsigned Night Run claim, with a clear alternate mode for a voided-race stake refund when raceId is provided. It is clear enough to distinguish from the sibling enter/back tools, though it does not explicitly name those alternatives.

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 implies when to use the tool: claiming winnings, or requesting a refund after a voided race via raceId. However, it does not explicitly compare against sibling tools such as prepare_night_run_enter or prepare_night_run_back, nor does it state prerequisites or exclusions.

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