onenote_help

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

No annotations are present, but this is a parameterless read-only discovery call, so the behavioral surface is minimal. The description discloses the return format explicitly (a Markdown string enumerating 19 tools with one-line usage notes), which is the key thing an agent needs to know.

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?

Front-loads the purpose, then uses headed sections (Return Format, Examples) for scannability. The Examples block is nearly content-free ('onenote_help()'), but overall it is tight and well-structured.

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?

An output schema exists, so return-value documentation is not strictly required, yet the description still summarizes the return format. For a trivial parameterless help tool, nothing an agent needs in order to call it is missing.

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 tool takes zero parameters, so the baseline of 4 applies. There is nothing for the description to clarify beyond the empty schema.

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?

States a clear verb+resource: 'List the available OneNote MCP tools and when to use each.' It is unambiguous and clearly distinct from the action-oriented siblings (list_pages, create_page, export, etc.), which an agent cannot confuse with a discovery/help tool.

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 that the tool documents when to use each of the 19 other tools, but never states when the agent itself should call this help tool (e.g., on ambiguous requests or at session start). Usage is implied rather than stated.

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