Call off a challenge

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

Adds real context beyond the annotations: the stake is returned, and the operation only applies to unaccepted challenges. That refund outcome is the most decision-relevant fact for an agent. It doesn't say what happens on an accepted challenge (error vs. no-op) or whether the action is idempotent.

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?

One compact sentence that front-loads the action and the gating condition, with the refund outcome appended. No filler.

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 one-parameter mutation with no output schema, the description covers action, precondition, and side effect (stake returned), which is nearly everything needed. Edge-case behavior (already-accepted challenge, repeat calls) is the only meaningful omission.

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% and the single parameter already documents accepted formats (play.terrace.social/c/<n> link or challenge number). The description adds nothing about the parameter, which is acceptable at this coverage level.

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?

Specific verb ('call off') plus specific resource ('a 1v1 challenge nobody has accepted yet'), which cleanly separates it from siblings like terrace_accept_challenge and terrace_challenge. An agent can pick this without reading any 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 precondition 'nobody has accepted yet' tells the agent when this tool is valid, which is the key gating condition. It doesn't name a sibling alternative or say what to do if the challenge has already been accepted, so it stops short of explicit when/when-not routing.

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