notion_create_page

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose the most critical non-obvious trait: the tool requires a file-first workflow and will not accept an inline JSON body. This is exactly the kind of hidden behavior that causes agent failures. It could additionally note side effects like duplicate creation on repeat calls, but the key behavioral trap is covered.

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?

Two sentences with zero wasted words. The critical warning is front-loaded in caps, and the purpose statement follows immediately. Every element earns its place, and the structure guides attention to what matters most.

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 two-parameter tool with fully covered schema, the description is nearly complete: it states the essential workflow, the payload requirements, and the creation context. The extract parameter in the schema already addresses return-field behavior, so the absence of an output schema is not a gap. Only minor details like failure behavior are missing.

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 100%, so the schema already documents both file_path and extract parameters well. The description reinforces the file_path requirement with emphasis and reiterates the payload structure, but adds little semantic value beyond what the schema provides.

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 states a specific verb and resource ('Creates page') with clear scope ('in database or as subpage'). This cleanly distinguishes it from siblings like notion_retrieve_page, notion_update_page, and notion_create_database without needing to inspect schemas.

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 gives clear operational guidance on the required workflow (write JSON payload to file, then pass file_path), but it never states when to prefer this tool over alternatives or when not to use it. Usage context is implied by the 'creates' framing rather than explicitly stated.

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