List pages

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

Beyond the readOnlyHint annotation, the description adds valuable behavioral context: result reports matched vs. shown counts, no offset is supported, no page content is returned, and default ordering is newest first. This helps the agent reason about output meaning without an output schema.

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?

Four sentences, front-loaded with the core purpose and followed by high-value caveats. Every sentence earns its place, with no redundant filler.

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 list tool with no output schema, the description covers result-count semantics, ordering, filtering strategy, and the key limitation (no offset). It also points to get_page for content, making it complete enough for correct invocation.

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 covers most parameters, and the description adds the key strategic point that narrowing is preferred over paging, plus the default ordering behavior. This meaningfully clarifies how limit, tags, locale, creator_id, and author_id relate to each other.

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?

Clearly states it lists pages with their metadata and specifies the default ordering (newest first). It also distinguishes itself from get_page by noting it returns no page content, so an agent can tell list from content-fetch behavior.

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?

Explains the no-offset limitation and explicitly tells agents to narrow via tags, locale, creator_id, or author_id rather than paging. It routes content needs to get_page, though it does not explicitly contrast with search_pages or grep_pages.

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