create-onenote-page

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

Annotations already indicate destructive and read-only hints. The description adds a critical behavioral note: the body must be a full HTML document, and partial HTML may fail silently. It does not cover other aspects like permissions or rate limits.

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 front-loaded with the purpose and includes a helpful tip. It could be slightly more concise but contains no unnecessary words.

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 description covers the key inputs and constraints (default notebook, section targeting, HTML requirement) but lacks information about the output (no output schema) and potential error scenarios.

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 covers 75% of parameters with descriptions. The description adds the crucial requirement that 'body' must be a full HTML document with specific tags, which is not in the schema and helps prevent errors.

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 clearly states it creates a OneNote page in the default section of the default notebook, and specifies how to target other sections via a query parameter. It distinguishes from siblings like 'create-onenote-section-page' which likely requires a specific section.

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 provides guidance on when to use this tool (default notebook) and how to use the sectionName parameter for other sections. It notes that the operation is only for the current user's default notebook, but does not explicitly list when not to use it (e.g., targeting other notebooks).

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