append_to_page

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

Discloses that content is appended as a new outline block at the bottom and supports HTML formatting. However, lacks details about error conditions, authentication requirements, rate limits, or what the output contains. With no annotations, the description carries the full burden but is partially complete.

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?

Concise three sentences plus parameter list. Front-loaded with the main action, then details, then parameter descriptions. No unnecessary words.

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?

For a low-complexity tool with two required parameters and an output schema (though not described), the description covers the core behavior and parameter usage. Missing description of the return value, but the output schema exists and can supplement. Overall adequate.

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?

Adds meaning beyond the schema by explaining page_id is from 'list_live_pages' and content can be plain text or HTML. Since schema description coverage is 0%, this is valuable. Could be enhanced with length limits or encoding details.

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?

Clearly states the action 'Append content' to a specific resource 'OneNote page'. Specifies it adds to the bottom of the page as a new outline block, distinguishing it from sibling tools like 'create_page' which creates new pages, and 'search_notes' which searches.

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?

Provides context by stating the page_id should come from 'list_live_pages'. Implicitly suggests use for appending to existing pages rather than creating new ones, but does not explicitly exclude use cases or mention alternative tools for updating or inserting content elsewhere.

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