get-onenote-page-content

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

Annotations declare readOnlyHint=true and destructiveHint=false, but the description adds no behavioral context beyond that. It does not disclose return format, potential size, or any side effects (though read-only). The description is minimal and fails to provide helpful behavioral details.

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 short (one sentence), which achieves conciseness but sacrifices clarity and completeness. It is not front-loaded with a clear purpose, and the sentence could be misinterpreted as a field description rather than a tool description.

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?

With no output schema, the description must explain the return value, but it only says 'HTML content' without clarifying format, metadata, or pagination. Given the complexity (4 params, many sibling tools), the description is severely lacking in completeness.

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 coverage is 100%, so the baseline is 3. The description does not add any parameter information beyond what the schema already provides, even though the schema itself has detailed descriptions for params like fetchAllPages.

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 'The page's HTML content.' states only the output, not the tool's action (e.g., 'retrieve' or 'get'). It essentially restates the tool name without adding an action verb, making the purpose vague.

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 on when to use this tool versus alternatives (e.g., list-onenote-pages, get-onenote-section-page). There is no mention of context, prerequisites, or exclusions.

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