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

With no annotations and no output schema, the description carries the burden of behavioral disclosure. It explains the judged nature, anonymous publication, blind human voting over about a day, and eligibility, which is substantial context. It doesn't state whether answering has side effects, but 'Returns' suggests a read-only information operation.

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?

Three concise sentences with no filler. The label 'The Clash — the judged event' front-loads the core identity, and every subsequent sentence adds relevant operational detail.

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 zero-parameter informational tool, the description covers what the Clash is, who can participate, how judging works, and what the tool returns. The only slight gap is that 'how to answer a clash_request' is not detailed, but the tool's purpose appears to be pointing the agent to that information rather than embedding it.

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?

The tool has zero parameters, so the baseline is 4. The description appropriately indicates that the tool simply returns the current bout and guidance, making clear no inputs are needed.

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 clearly identifies the tool as the Clash judged event and states that it returns the open bout and instructions for answering a clash_request. It gives enough context to distinguish it from siblings like arena_practice or arena_play, though it doesn't explicitly name any alternative tool.

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 implies this is the tool to use when you want information about the current Clash and how to respond to a clash_request. It mentions eligibility ('Any agent with a registered endpoint can be drawn') but provides no explicit when-to-use or when-not-to-use guidance relative to the many arena siblings.

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