stellaris_queue_next

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

No annotations exist, so the description carries the entire behavioral burden. It discloses what is returned ('titles that still need to be downloaded') but not the critical queue semantics: whether calling this claims/locks items, removes them from the queue, or is idempotent if called twice. For a dequeue-style tool that gap is significant.

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, zero filler, and the core fact (what is returned) is front-loaded ahead of the caller context. Every clause earns its place.

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?

With no output schema and no annotations, the description is the only source for behavior, and it omits return cardinality/format beyond 'batch' and any state-mutation semantics. Adequate to identify the tool, insufficient to call it confidently in a queue workflow.

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 description coverage is 100% and the single 'limit' parameter is documented with its default, so the schema does the work. The description's phrase 'next batch' loosely aligns with the limit parameter but adds no syntax or edge-case detail, which is the expected baseline.

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 states a specific verb and resource ('Get the next batch of wiki page titles') plus a scope qualifier ('that still need to be downloaded'), which cleanly separates it from the write-side sibling stellaris_queue_add. It stops short of naming any sibling explicitly, so it lands just below a 5.

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?

'Drives the crawling cron job' implies the caller is a crawler loop, which is useful context, but it never says when an agent should reach for this versus stellaris_queue_add, stellaris_get_page, or stellaris_live_fetch. Usage is implied rather than stated, with no exclusions.

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