enoch_review_next

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds minimal behavioral context. It does not explain what happens if no unreviewed candidates exist, or how 'next' is determined.

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?

The description is very concise (single sentence), but it omits essential information. It is not optimally front-loaded because it lacks parameter and usage details, making it under-specified rather than efficiently concise.

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?

Given the tool has one undocumented parameter and no output schema, the description is severely incomplete. It does not cover return values, edge cases, or behavioral nuances, which are critical for an AI agent to invoke the tool 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?

The sole parameter 'paper_status' (default 'publication_draft') is entirely undocumented in the description. With 0% schema description coverage, the description fails to clarify its purpose or allowed values, leaving the agent without crucial semantic guidance.

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 clearly states the action ('Get') and the resource ('next unreviewed publication review candidate'), which distinguishes it from sibling tools like enoch_review_list or enoch_review_claim. However, it lacks specificity on the ordering criteria for 'next'.

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 description provides no guidance on when to use this tool versus siblings (e.g., enoch_review_claim, enoch_reviews_list). There is no mention of prerequisites, alternatives, or typical workflow context.

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