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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the claim is bounded to one task, and it returns no assignment when nothing is available (implying an empty-result path rather than an error). It omits auth requirements (node_token), whether check-in mutates server-side node state, and any rate/retry behavior.

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?

Two short sentences that are front-loaded and free of filler. Slightly under-informative rather than verbose, and 'worthwhile' is an undefined criterion, but nothing is wasted.

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?

A 5-parameter tool with no annotations, no output schema, and zero schema descriptions leaves the agent guessing about the token, capability/language filtering semantics, and the shape of a returned assignment. The description covers only the claim count and the empty-result case, which is far short of what is needed.

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?

All five parameters (node_token, host, languages, capabilities, user_agent_label) have 0% schema description coverage, and the description explains none of them. At best 'contributor node' vaguely implies node_token is an identity credential, leaving the other four undocumented anywhere.

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 (check in) and resource (contributor node) plus the concrete effect of claiming at most one Tier-0 task. It implicitly differentiates from register/submit siblings by describing a recurring, automatic check-in rather than a one-time registration, though it never names those siblings.

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 word 'automatically' hints this is a polling/loop entry point, but there is no explicit when-to-use guidance, no prerequisite (e.g. node_token must exist, so register first), and no mention of alternatives like contributor_register or contributor_set_status.

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