create-onenote-section

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

Annotations indicate destructiveHint=true and openWorldHint=true, which the description's 'Create' verb aligns with. However, the description adds no additional behavioral context such as side effects, permissions, or rate limits beyond what annotations provide. With annotations present, the bar is lower, but minimal extra value is given.

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: two sentences with a clear purpose and a helpful tip. No wasted words, and the key information is front-loaded.

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 complexity (4 parameters, nested body, no output schema), the description is too brief. It does not mention what the tool returns upon success (e.g., the created section object), error conditions, or prerequisites like which notebookId to use. This leaves significant gaps for an 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?

Schema description coverage is 75%, and the description adds a concrete example of the body parameter ('Body: { displayName: 'Section Name' }'), which helps clarify usage. However, it does not explain other parameters like includeHeaders or excludeResponse, and the nested body schema is complex without further guidance.

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') and the resource ('onenoteSection') along with the context ('in the specified notebook'), matching the tool name and distinguishing it from sibling tools like create-onenote-page.

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 a tip with an example body, implying the required parameter, but does not explicitly state when to use this tool versus alternatives (e.g., when to create a page or notebook instead), leaving the agent to infer usage context.

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