Create Notion Page

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

Annotations already indicate non-read-only and non-destructive behavior. The description adds 'Risk: safe_write', clarifying that it is a write operation but safe (no unintended damage). This extra context slightly raises transparency, though more details (e.g., permission requirements) could be added.

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 extremely concise: two sentences, no wasted words. Every sentence adds value (purpose and safety hint). It is front-loaded with the action and location, making it easy to scan.

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 4 parameters with no schema descriptions, no output schema, and no explanation of content format (e.g., Markdown), the description is too brief. It lacks details on default behavior (e.g., root page if parentPageId omitted), return values, and prerequisites, making it incomplete for effective invocation.

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% (no parameter descriptions). The description mentions 'parent page' which relates to the optional 'parentPageId', but provides no further meaning for parameters like 'title', 'content', or 'requestingAgent'. It fails to compensate for missing schema descriptions, leaving agents to guess formats or constraints.

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 verb 'create' and the resource 'Notion page', and specifies the location context ('under the configured root page or provided parent page'). This distinguishes it from sibling tools like 'notion_append_to_page' (which appends to an existing page) and 'notion_get_page' (which retrieves).

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 implies use for creating new pages, but provides no explicit guidance on when to use this tool versus alternatives (e.g., 'notion_append_to_page' for adding content to an existing page). No when-not or alternative scenarios are mentioned, leaving the agent to infer from context.

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