list-site-onenote-pages

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

Annotations already cover the safety profile with readOnlyHint, idempotentHint, and destructiveHint false, so the description does not need to restate that this is a non-mutating operation. The description adds little behavioral context beyond the SharePoint-site scope; pagination and cursor behavior are documented in the schema rather than the description. No contradiction with annotations.

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: it states the action and the resource scope directly. It does not repeat information already present in the schema or annotations.

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?

The tool is minimally viable for a read-only listing operation because annotations and schema documentation are strong. However, with no output schema and no explanation of return shape or how this tool relates to sibling OneNote page tools, the description leaves some contextual gaps.

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 100%, so the baseline is 3; the description itself adds no parameter-level semantics. The schema already documents cursor, filter, search, orderby, siteId, and maxItems with clear examples and pagination notes.

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 uses specific verbs ('List/search') and a precise resource: OneNote pages of a SharePoint site's notebooks. It is clear in scope but does not explicitly distinguish itself from closely related siblings like list-site-onenote-section-pages or search-onenote-pages.

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?

There is no guidance on when to use this tool instead of alternatives such as list-site-onenote-section-pages or search-onenote-pages, nor when to prefer search vs filter. The agent must infer usage from the tool name and parameters.

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