read_live_page

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the two output modes (Markdown vs raw XML) and the scope of content read, but says nothing about authentication requirements, whether reading a live page has side effects or caching implications, or error behavior when an identifier fails to resolve. It is informative about output but thin on operational traits.

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 purpose is front-loaded in the first sentence, followed by a compact argument list. Every line earns its place with no filler or repetition, though the Args block is a slightly verbose way to carry parameter semantics that could be tightened.

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 required, and the description nonetheless states the output formats. All five parameters are covered, including fallback logic. The remaining gap is operational context (auth, failure modes) for a live-service read tool with no annotations, which keeps it short of a 5.

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 0%, so the description must compensate, and it does: all five parameters are documented with meaning, including that page_id is the persistent ID sourced from list_live_pages and that notebook_name/section_name/page_title are conditional fallbacks used only when page_id is absent. This conditional relationship between parameters is genuinely additive, though default values and the matching semantics of the page_title substring are not fully spelled out.

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 first sentence gives a specific verb (Read), a specific resource (a live OneNote page), and enumerates returned content (full text, tables, hierarchical sub-bullets) plus output formats (Markdown or raw XML). It clearly reads rather than mutates, distinguishing it from write siblings like create_page/update_page_content. It does not, however, explicitly differentiate itself from read_section or search_notes, which also retrieve content.

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?

Usage guidance is implicit: the page_id arg points to list_live_pages as the source, and the description explains the fallback path (notebook/section/page_title) when page_id is absent. That tells the agent how to locate a page but not when to prefer this tool over read_section or search_notes, and there are no exclusions or preconditions stated.

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