List Pages

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

Despite no annotations, the description explains pagination behavior (cursor-based, limit, nextCursor), preview behavior, and auto-detection of organization. It lacks explicit statement of read-only nature but implies it via listing semantics.

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 well-structured with the main verb-resource phrase first, followed by three informative sentences. It avoids redundancy but each sentence adds necessary 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?

Given no output schema, the description covers key response metadata (total count, hasMore, nextCursor) and distinguishes between full content and previews. It could mention the page object shape but is sufficient for a list endpoint.

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%, and the description adds contextual value by explaining the auto-detection of organization, the effect of previewOnly, and pagination details. This enriches the schema definitions.

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 clearly states it lists all pages for the organization in Magnet with markdown content, specifying the previewOnly option. It distinguishes itself from siblings like get_page_by_id and create_page by focusing on bulk listing.

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 provides clear context on when to use the tool, mentioning automatic organization determination, previewOnly mode, and pagination. However, it does not explicitly contrast with search or list_issues for filtering needs.

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