wikijs_list_pages

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

With no annotations provided, the description carries the full behavioral disclosure burden. 'List pages with pagination' does communicate a read-only enumeration operation and the existence of pagination, but it omits details like ordering, whether returned entries are summaries or full page content, and pagination edge behavior.

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 a single, front-loaded sentence with no wasted words. It efficiently conveys the core operation and a key behavioral trait, even though it does not provide deeper detail.

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 simple two-parameter, no-required-fields tool, the description plus fully documented schema is mostly enough to invoke the tool. However, without an output schema and without any note about return shape, ordering, or the difference from search_pages, the description leaves some gaps for an agent deciding how to interpret the result.

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 input schema fully describes both limit and offset with defaults and meanings, so the schema carries the descriptive weight. The description's word 'pagination' only loosely parallels those parameters and adds no new constraints, ranges, or formatting details, warranting the baseline 3.

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 ('List') and resource ('pages'), with a pagination qualifier that clarifies the operation's mode. It is clear but does not explicitly differentiate list_pages from sibling tools like wikijs_search_pages or wikijs_get_page, so it falls short of 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?

No guidance is given about when to use this tool versus alternatives such as wikijs_search_pages or wikijs_get_page. The description states what the tool does but does not provide usage context, exclusions, or a decision rule for selection.

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