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

Despite annotations carrying no positive hints (readOnlyHint=false, destructiveHint=false, etc.), the description discloses the permanent freeze behavior: 'Moving TO LOCKED also freezes every submission record permanently — a later rollback to SUBMIT reopens the window for NEW teams but does NOT unfreeze already-locked ones.' This is critical behavioral context beyond annotations, including return values and required scope.

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 information-dense yet well-structured, front-loading the core action and then explaining caveats in order of importance. Every sentence adds value: the phase list, the single-lever role, the permanent-freeze gotcha, the backwards-move rationale, and the structured Args/Returns/Scope. 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 state machine with subtle irreversible behavior, the description covers purpose, side effects, allowed extension, required scope, and return shape. It is missing explicit guidance on the eid parameter and whether forward phase jumps (e.g., PRE to RESULTS) are allowed, but given the absence of an output schema and sparse annotations, it is remarkably complete.

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 0%, so the description must compensate. It adds deep meaning to the phase parameter by mapping phases to real-world events and explaining side effects of LOCKED. However, the 'eid' parameter is only listed as 'eid?' with no explanation of what it identifies or when it is needed, leaving a small semantic gap.

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 opens with a specific verb and resource: 'Move the event through PRE -> OPEN -> BUILD -> SUBMIT -> LOCKED -> JUDGING -> RESULTS.' It clearly distinguishes this as the single phase-transition lever for hackathon lifecycle, differentiating it from sibling admin tools by stating 'One call gates every write surface.'

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 provides explicit usage context: 'this is the single lever for registration closes, submissions close, results are public.' It also gives guidance on backwards moves: 'Backwards moves are allowed on purpose (deadline extensions are real),' telling agents when to use this tool for extensions. Required scope conditions are stated, though no alternative tool is named since none exists.

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