create-onenote-section

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

Annotations already indicate destructiveHint=true and openWorldHint=true, so the description's assertion of creation aligns. It adds the tip about body format, but does not disclose additional behavioral details (e.g., side effects, permissions).

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 very concise, using two sentences and a tip. It is front-loaded with the core purpose and provides just enough extra 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?

Given the tool's complexity (nested objects, 4 parameters, no output schema, destructive behavior), the description is too minimal. It lacks details on return values, error conditions, and confirmation that the section was created successfully.

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?

With schema description coverage at 75%, the baseline is 3. The description adds value by explicitly highlighting the required displayName field in the body, simplifying the complex nested schema for the agent.

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 tool creates a new OneNote section in a specified notebook using a specific verb ('create') and resource ('onenoteSection'). It distinguishes well from siblings like create-onenote-page and create-onenote-notebook.

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 is provided on when to use this tool versus alternatives, such as create-onenote-section-page or list-onenote-notebook-sections. Prerequisites (e.g., notebook must exist) and exclusions are missing.

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