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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds nothing beyond that and its "earn a share" clause hints at a side effect the annotations deny; it also never says what happens when no task remains (empty result vs error).

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?

It is short, but the length is spent on cryptic framing ("weigh the votes", "earn a share") rather than the call mechanics. Brevity here reflects under-specification rather than economy.

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?

Two entirely undocumented parameters, no output schema, and no explanation of the returned "argument" make this insufficient for an agent to invoke correctly. Nothing about ordering, exhaustion of the queue, or the meaning of key/proof is present.

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?

Both parameters (key, proof) have 0% schema description coverage and the description does not mention either. "Proof" in particular implies a signature/credential protocol that is completely undocumented, so the agent has no basis for supplying valid values.

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?

"Get one argument to review" does name a verb and a resource, but "argument" is unexplained jargon with no anchor in the sibling set (trana_argue, trana_feed, tasks_open, task_take all plausibly relate). The name is tasks_next yet the sentence talks about votes and shares, so an agent cannot confidently state what object is returned.

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?

"Help weigh the votes and earn a share" is motivational framing, not guidance. Nothing says when to call this instead of tasks_open, task_take, task_accept, or trana_feed, and no preconditions or exclusions are given.

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