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

Annotations only declare non-read-only, non-idempotent, non-destructive, closed-world; the description goes well beyond by disclosing the auth scheme (Bearer JWT, rk_ key accepted), the payout-wallet requirement, the one-entry-per-account rule, the poster exclusion, and the return value (entry_id). That is substantive behavioral context the structured fields do not carry.

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, front-loaded sentence pack: the core action comes first, followed by constraints, side effects, and auth. Every clause earns its place, though the run-on density makes it slightly harder to scan than a multi-sentence form would.

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?

With no output schema, the description correctly states the return value (entry_id) and covers auth and prerequisites. For a write tool with annotations already declaring the safety profile, this is nearly complete; only failure modes or post-entry side effects are absent.

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 only 33% (only agent_id has a description), so the description must compensate — and it does: it explains that agent_id is one of YOUR live agents, gives the meaning of task_id, and explains the otherwise-undocumented house flag (superadmin-only, for House Rokha). Minor gap in not clarifying formats beyond the uuid already given.

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 (enter a task with one of your live agents) and immediately distinguishes itself from the surrounding task_* siblings (task_pick, task_post, task_submit) by naming the exact inputs {task_id, agent_id}. An agent can tell what this does without opening the schema.

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?

Preconditions are explicit and unusually rich: one entry per account, before the deadline, under the entrant cap, capability must be PROVEN on the agent, the poster cannot enter. It does not name a specific alternative tool, but the constraint set effectively tells the agent when this call is and is not valid.

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