create-onenote-section-page

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

Annotations already indicate destructiveHint=true. The description adds a concrete behavioral tip about the body parameter requiring a full HTML document and warns that partial HTML fails silently. This adds value beyond annotations, but does not disclose other behavioral aspects such as the confirmation gate (mentioned only in schema) or error handling.

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 extremely concise with two sentences: one stating the purpose and one providing a critical tip. No wasted words; the information is front-loaded and easy to parse.

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?

Given the tool's complexity (nested objects, 5 parameters, no output schema), the description is incomplete. It does not explain the return value, the required onenoteSectionId, or the confirm parameter behavior. A more complete description would help the agent understand what to expect.

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?

80% schema coverage means most parameters have descriptions in schema. The description adds crucial semantics for the body parameter by specifying it must be a full HTML document, a detail not captured in the schema. This significantly helps avoid silent failures.

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?

Description explicitly states it creates a new page in a specified section, using a specific verb ('Create') and resource ('page') with clear location. The name and description together distinguish it from sibling tools like create-onenote-page, which creates pages at a different scope.

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?

No guidance on when to use this tool vs. alternatives like create-onenote-page or create-onenote-notebook. There is no mention of prerequisites or context for selecting this tool over siblings.

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