Onenote Create Page

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

With no annotations provided, the description carries the full burden and does so well. It discloses that bodyText is written as a single plain-text paragraph, that the owning notebook is checked against an allowlist before any write, and that refusal produces a specific [onenote_notebook_not_allowed] error. This is meaningful behavioral context.

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 compact and front-loaded, with the core action in the first clause. Every sentence carries useful operational detail: canonical format, source of valid IDs, bodyText behavior, allowlist check, and error outcome. There is no padding.

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 write action with no annotations, the description is unusually complete: it covers input sources, format constraints, a security precondition, and error behavior. The main missing piece is the semantics of the required title parameter, which keeps it from a 5.

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 must compensate. It adds strong semantics for sectionId (canonical form, source, non-resolving alternatives) and bodyText (plain-text paragraph), but the required title parameter is never described. This is a clear gap for a required argument.

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 a specific verb and resource: 'Create a new page in the OneNote section identified by sectionId.' This clearly differentiates the tool from siblings like onenote_get_page and onenote_update_page, even without explicitly naming them.

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 clear context: it is for creating a page, and it tells the agent to obtain sectionId from onenote_list_sections or onenote_search rows. It does not explicitly state when not to use this tool or mention onenote_update_page as an alternative, so it stops short of a 5.

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