next_wiki_article

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

Annotations declare readOnlyHint=false, consistent with 'next page' implying a stateful cursor advance. The description adds a return-format hint (JSON header plus page), which is useful, but does not confirm that pages are consumed or what happens after the last page. Adequate but thin for a stateful iterator.

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 that states the action and the extraction context with no filler. Slightly dense parenthetical, but nothing wasted.

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 no output schema and only two annotations, the description leaves open iteration termination, page-size defaults, and how the returned header relates to run state. It is enough to attempt a call but not enough to confidently drive the pagination loop.

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 100%, so uid, run_id, and max_pages are already documented in the schema (including the subagent ownership case for uid and the run_id pattern). The description adds no parameter-level detail beyond the schema, which is the baseline 3 when the schema does the work.

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 concrete verb and resource: 'Get the next page of article text.' The purpose of feeding entity extraction is clear. It does not, however, differentiate itself from the sibling get_article_page, which an agent could plausibly confuse it with.

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 implies a pagination loop ('the next page') but never says when to call this versus get_article_page, what ends the iteration, or what run state is required. Usage must be inferred from the schema and the sibling list.

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