next_screening_batch

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

Annotations only declare readOnlyHint=false and openWorldHint=false. The description says 'Get', which reads like a passive read, yet it never explains that calling it advances/consumes the screening queue, whether items can be re-fetched, or what happens if the batch is not recorded. For a state-advancing 'next' tool this is a notable disclosure gap.

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, front-loaded sentence with no filler; the verb and scope come first. It is efficient, though very terse given the workflow it participates in.

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?

An output schema exists, so return values need not be explained. However, for a two-parameter, non-read-only queue tool, the description omits prerequisite sequencing, iteration behavior, and batch_size semantics, leaving the agent with a minimum-viable picture.

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%: run_id is documented only as 'Run ID from start_search', and batch_size carries no description at all in the schema. The description does not compensate by explaining batch_size limits/semantics or how run_id links to start_search, so the undocumented parameter remains opaque.

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 ('Get') and resource ('next unscreened titles/abstracts'), plus the payload detail that screening criteria are returned alongside. That distinguishes it reasonably well from fetch_articles/list_articles, though it doesn't name any sibling explicitly to route the agent.

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?

Usage is only implied: mentioning 'unscreened' and 'criteria to judge them against' signals it belongs inside the screening loop, but there is no explicit when-to-use, no prerequisite (start_search/set_screening_criteria first), and no pointer to record_screening_decisions as the follow-up.

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