List pages

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the description's job is lighter. It adds useful behavioral context: default sort order ('most recently modified first') and the scoping rule for section, which are not fully captured by annotations. It does not contradict the annotations and avoids describing destructive effects.

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 filler. Every phrase earns its place by communicating ordering and scoping behavior in a compact form.

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 the simple list operation, the three optional parameters are well documented in the schema, and the description covers default ordering and scoping. However, it doesn't clarify the return shape or when to prefer searchPages, leaving a minor completeness gap in the absence of an output schema.

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 schema already provides 100% parameter coverage, including descriptions for limit, orderBy, and section. The description adds a small clarification that omitting section lists across all sections, which is helpful but not a substantial addition beyond the schema.

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 opens with 'List pages,' a specific verb+resource, and adds 'most recently modified first' to convey default ordering. It also clearly states the section scoping behavior, distinguishing it from sibling tools like listNotebooks and listSections, though it doesn't explicitly contrast with searchPages.

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 gives conditional usage for the section parameter ('Pass a section NAME to scope...; omit it to list across all sections'), but it provides no guidance on when to choose listPages over searchPages, getPage, or other siblings. There are no exclusions or alternatives named, so usage context is only implied.

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