notion_create_page

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=true), so the bar for added disclosure is lower. The description adds useful context: content_markdown is converted to Notion blocks, effect is a claimed read/write effect that 'Spring verifies,' and approval_ref is required when resuming a write. No contradiction with annotations exists — 'create' is consistent with readOnlyHint=false, and the description never claims read-only behavior. However, it does not disclose Notion-side side effects such as visibility, required permissions, or failure behavior on Markdown conversion.

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 definition is well-structured: a crisp front-loaded summary sentence followed by a readable Args block with one short line per parameter. Every line earns its place, though the empty title line and the circular project_ref phrasing could be tightened. The format is scannable for an agent.

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 the description's job, and annotations cover the mutation/idempotency profile. For a 9-parameter tool with 0% schema coverage, the description documents most params adequately. However, it leaves gaps: no sibling-routing guidance, title is undefined, the required/optional conflict is unresolved, and there is no indication of which parameters a minimal valid call actually needs.

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's Args block carries the entire documentation burden. It provides meaningful one-line semantics for 8 of 9 parameters (parent_id, content_markdown, project_id, project_ref, connector_account_ref, idempotency_key, effect, approval_ref). Gaps remain: title has an empty description, project_ref ('Exact project correlation reference') is nearly circular, and the 'required' tags on parent_id/title conflict with the schema, which marks all 9 parameters as optional with null defaults.

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 opening sentence uses a specific verb+resource: 'Create a new Notion page in the given parent (database or page).' This clearly separates it from sibling create-tools like notion_create_database, notion_create_comment, and notion_create_view, and from update-tools like notion_update_page. The parent qualifier (database or page) adds useful scope precision.

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 is given on when to select this tool over its numerous Notion siblings (notion_create_database, notion_update_page, notion_append_block_children, notion_replace_page_markdown). With roughly 50 notion_* siblings present, the agent must infer selection purely from the tool name. No exclusions, no 'use X instead for Y' routing.

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