create-onenote-page

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

Annotations already indicate write operation (readOnlyHint=false) and potential destructiveness (destructiveHint=true). The description adds a tip about the body requiring full HTML and that partial HTML fails silently or creates malformed pages, which is helpful. However, it does not disclose other behaviors like authentication or side effects.

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 concise, with two paragraphs that front-load the purpose and usage, followed by a critical tip. Every sentence adds necessary information without redundancy.

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?

Despite the complex input schema, the description omits the return value (e.g., the created page object) and does not explain the response format. The tip is useful, but the lack of output schema and missing response description leaves information gaps for the agent.

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 67% of parameters with descriptions, and the description adds value by clarifying the need for full HTML in the body and mentioning the sectionName query parameter not present in the schema. This helps beyond what the schema provides.

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 that the tool creates a new OneNote page in the default notebook's default section, and explains how to target a different section via the sectionName query parameter. It distinguishes from the sibling create-onenote-section-page by specifying the default section 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?

The description explains when to use the tool (create page in default notebook or with sectionName) and when not to (targeting other notebooks). It mentions an alternative for other notebooks but does not explicitly name sibling tools, leaving room for improvement.

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