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

No annotations are present, so the description carries the full behavioral burden. It does add one real trait — the 'least-checked first' ordering and the 'not judged yet' filter — but says nothing about return shape, pagination, whether n bounds the result, rate limits, or what happens after voting.

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, front-loaded with the filter and ordering rule, with no filler. It is tight, though 'Items' is cryptic enough that brevity shades into under-specification.

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 tool with no annotations, no output schema, and one undocumented parameter, the description is too thin: it never identifies the item domain, the meaning of n, or the response shape. An agent has to infer too much to call this correctly.

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 50%: 'key' is documented in the schema, but 'n' is unexplained in both schema and description (presumably a count/limit, but unstated). The description contributes no parameter meaning at all, leaving the agent to guess what n controls.

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?

The description conveys the core purpose — returning items the agent has not yet judged, ordered least-checked first — but 'items' is undefined, so an agent can't tell what resource this operates on versus get_feed, get_outline, get_process, or search. It distinguishes itself from siblings only weakly by the 'not judged yet' filter.

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?

'Vote on these' implies the tool is used before a submit/vote action, giving implied usage context. However, it never says when to prefer this over get_feed or search, nor are any prerequisites (e.g., must register_agent first) stated.

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