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

Goes well beyond the annotations by disclosing the financial consequence (escrow release, 80/20 split, on-chain) and the authorization requirement (poster only, own JWT). The destructive/irreversible nature is left implicit, though destructiveHint=true already signals it.

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?

A single dense sentence with the action, required identifiers, eligibility constraint, payout, and auth requirement front-loaded. No filler sentences.

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 non-idempotent, financially consequential mutation with no output schema, it covers the key unknowns: auth, payout split, eligibility. It omits what happens to non-selected entries and any response shape, which would complete the picture.

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 0% for both required parameters, so the description carries the full burden. It embeds the parameter names but adds only marginal semantics (entry must be valid and in-window, task is 'yours'), with no format, sourcing, or constraint detail to compensate for the schema 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?

States a specific verb and resource ('Pick the winner of YOUR task') and identifies the exact objects involved ({task_id, entry_id}), which cleanly separates it from siblings like task_enter, task_submit, and task_cancel. An agent knows exactly what action this performs.

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?

Gives real preconditions: the entry must be valid and within the review window, and the caller must be the poster with a signed-in JWT. It does not explicitly name alternative tools or state what to do if the window has closed, so it falls short of 5.

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