createPage

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

Annotations already indicate non-idempotent and non-destructive. Description adds only the XHTML content requirement, lacking details about side effects, authentication needs, or failure modes (e.g., what happens if sectionId is invalid).

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?

Single sentence with minimal words, no redundancy. However, it is slightly underspecified for the parameter context; could be improved with a brief usage note but remains efficient.

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?

With 3 required params, no output schema, and minimal annotation detail, the description lacks important context such as return value behavior, duplicate handling, or size limits. Incomplete for effective agentic use.

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 has 3 required params with 33% description coverage (only contentHtml described). The description adds no extra meaning for title or sectionId beyond their names and types, failing to compensate for low schema coverage.

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 the action (create), the resource (OneNote page), and the specific context (exact section, using XHTML content). It distinguishes from siblings like listPages (read-only) and searchPages (search).

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 listSections or getPage. No prerequisites or exclusions mentioned, leaving the agent to infer usage without explicit context.

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