list_live_notebooks

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

The description discloses it uses the OneNote COM API and shows notebooks currently open in the desktop app, including sections. Without annotations, this provides adequate behavioral context, though it could mention that it only shows live notebooks, not cloud-only ones.

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 two short sentences, front-loaded with the main purpose in the first sentence, followed by a contextual sentence. Every sentence adds value 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 has zero parameters, an output schema exists (so return values are documented elsewhere), and the description includes relevant context about COM API and live notebooks, it is fully sufficient for the agent to use correctly.

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?

There are zero parameters, so schema description coverage is 100%. The description does not need to add parameter information, and it provides baseline value by clarifying the tool's purpose.

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 lists live notebooks from the running OneNote app, distinguishing them from backup files, and notes it includes sections. This provides a specific verb and resource, differentiating it from siblings like list_notebooks.

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 explicitly says 'Use this to find where to create new pages,' giving a clear use case. However, it does not mention when to use alternatives like list_notebooks or get_notebook_summary, nor does it state when not to use this tool.

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