onenote_list_pages

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

No annotations are provided, so the description carries the full disclosure burden. It does reveal that omitting section_id switches to a cross-notebook 'most recently modified' mode, which is genuinely useful behavioral context, but it says nothing about ordering, recency windows, pagination, or how many results a 'recent pages' call returns.

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 sentence, front-loaded with the primary section-scoped use case and the fallback mode immediately after. No 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?

An output schema exists, so return values need not be explained. For a 2-parameter read tool with no annotations and zero schema descriptions, though, the description should say more about the limit parameter and result ordering; the 'most recently modified' claim is asserted without any definition.

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 description coverage is 0%, so the description needs to compensate and only partly does. It implies section_id's meaning and its optional alternative mode, but the 'top' parameter is never mentioned — no default of 20, no maximum, no note on what it limits in the cross-notebook mode versus the section mode.

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 gives a specific verb (List) and resource (pages) plus a two-mode scope: within a section, or the user's recently modified pages across all notebooks. That cleanly separates it from onenote_get_page (single page) and largely from onenote_search_pages, though the search sibling is never named as a contrast point.

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 two modes are described, which implicitly tells the agent when each applies, but the trigger conditions are left to inference. It never states when to choose this over onenote_search_pages, nor what the default behavior is when no section_id is supplied.

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