Lists project pages with id, name, fileName, section count, and selection status. Use this to avoid guessing page names before selecting or linking pages.
List the project's pages (id, name, fileName, section count, which one is selected). Call this instead of guessing a page name for select_page or link_page.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.8.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description itself must convey behavior. 'List' communicates a read-only operation, and the parenthetical enumerates exactly what will be returned. It does not mention prerequisites or errors, but for a zero-parameter listing tool this is minor.
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 concise sentences; the first states the operation and output fields, and the second provides routing guidance. No filler or 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?
For a zero-parameter, no-output-schema listing tool, the description covers operation, output fields, and when to call it. The only unstated detail is the exact JSON shape, but the field list makes it inferable.
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 has no parameters, so there is no input ambiguity to clarify. The description adds value by naming the output fields an agent can expect, which is more useful than parameter documentation here.
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 ('the project's pages'), and enumerates the returned fields (id, name, fileName, section count, selected). This clearly differentiates it from sibling page-related tools like select_page and link_page by showing it is the read-only enumeration operation.
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?
Explicitly instructs the agent to call this instead of guessing a page name for select_page or link_page, naming the sibling tools it should precede. This gives clear when-to-use guidance, even though it doesn't enumerate all alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.