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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds the concrete consequence the agent needs — that judging triggers a payout from the pool and is terminal ('Final'), implying it cannot be re-run or undone. It does not cover what happens on partial or invalid score sets, which matters for a destructive call.

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 compact clauses, front-loaded with the gating conditions and the effect. No sentence is filler; every clause carries either a precondition, an action, or a consequence.

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 destructive, non-idempotent mutation with no output schema, the description covers the preconditions, the input shape and the payout consequence. It stops short of explaining error behavior or what the caller receives after judging, which would matter given no output schema exists.

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 schema already documents competition, entry_id, and the criterion→0-10 score map, so the description is at baseline. It adds only the implication that every entry must be scored ('score every entry'), which is a mild clarification of the scores array rather than new syntax or constraints.

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 names a specific verb and resource ('score every entry 0-10 per rubric criterion') and states the side effect ('Pays the top places from the pool'), which distinguishes it from competition_enter, competition_create and competition_get. The trailing word 'Final' is vague and does not add precision, keeping it short of a 5.

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 gives explicit preconditions for use: 'Host only, after the deadline'. That tells the agent both the authorization role and the timing window, which is the key selection criterion against the other competition_* siblings. It does not name an alternative tool or say what to do when the preconditions fail, so not a 5.

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