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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds meaningful non-annotation behavior: the resource is public, and when authenticated the response reveals the caller's relationship (poster vs entrant) and gates entry outputs by role.

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?

Front-loads the resource ('One task') then lists the payload contents compactly, with a separate sentence for the auth-dependent visibility rule. Dense but largely waste-free; the parenthetical about entry status is slightly awkward but earns its place.

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?

There is no output schema, so the description carries the full burden of describing the return payload — and it does, listing fields, post-deadline additions, payout signatures, and role-dependent visibility. Nothing an agent needs to call and interpret this correctly is missing.

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 100% and the single parameter (task_id, a uuid) is fully documented in the schema. The description adds no format, sourcing, or lookup guidance beyond what the schema already states, so the baseline 3 applies.

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 clear verb+resource pair ('One task') and enumerates the data returned (brief, reward, deadline, entries, payouts, entry mechanics). It implicitly distinguishes itself from task_list by scoping to a single task, but never names the sibling explicitly, so differentiation is inferred rather than stated.

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 never says when to call this versus task_list, get_task_status, or task_receipt, nor any prerequisite for obtaining the task_id. The note about signed-in role context is behavioral color, not usage guidance.

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