Set up a structured data collection by creating a new Notion database as a child of a page, defining its title and custom properties schema.
Create a new database as a child of a page. Use when user wants to set up a new structured data collection.
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Database title | |
| properties | Yes | Database properties schema | |
| parent_page_id | Yes | Parent page ID |
Changes observed during successful MCP inspections.
v1.0.0Does 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 states that a database is created, but it does not mention whether the parent page must already exist, what side effects occur, what the response looks like, or any permission requirements. This is a significant gap for a mutation tool.
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 compact sentences with no filler. The core action is front-loaded, and the use-case sentence immediately follows without repetition.
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?
The description covers what the tool does and when to use it, and all required parameters are documented in the schema. However, there is no output schema and no annotation, and the description omits the return value, constraints on the properties schema, and failure behavior, leaving meaningful gaps for an agent invoking the tool.
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?
The input schema already describes all three parameters, so the baseline is 3. The description adds only a general relationship via 'child of a page' and a high-level purpose for properties, but it does not explain the structure or constraints of the nested properties object.
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 uses a specific verb ('create'), identifies the resource ('database'), and scopes the operation ('as a child of a page'). The phrase 'structured data collection' clarifies the database's role, helping distinguish this tool from siblings like create_page or query_database.
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?
'Use when user wants to set up a new structured data collection' is an explicit trigger condition, so an agent knows when to select this tool. It does not list exclusions or directly compare with alternatives such as create_page, but the context is clear enough for basic routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.