list_pagesList all guide pages in reading order with section, title, and one-line summary, so coding assistants can navigate the AIOTIC Integrator Guide.
All pages of the guide with section, title and one-line summary, in reading order.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully discloses the return contents and that results are ordered by reading sequence, which is real behavioral context for a listing tool. It says nothing about pagination, completeness guarantees, or whether the listing can change.
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 zero filler; the scope, returned fields, and ordering are all packed into one clause without redundancy.
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 parameters, no annotations, and no output schema, the description must convey the return shape itself, and it does so concisely (section, title, summary, ordering). Remaining minor gap is any hint about list size or pagination.
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 tool takes zero parameters, so there is nothing to document; the baseline of 4 applies. No parameter-level information is needed or missing.
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 (list) and resource (guide pages) and even enumerates the returned fields (section, title, one-line summary) plus ordering semantics (reading order). It does not, however, name or contrast with siblings like search_guide or get_page, so an agent must infer the distinction.
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 phrase 'in reading order' implies the browsing/enumeration use case, so usage is inferable. But there is no explicit when-to-use guidance, no statement of when to prefer search_guide or get_page, and no exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.