notion_create_database

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

With no annotations provided, the description carries the full burden. It does disclose that the database appears as an inline database on the page and that a title property is required, which adds behavioral context. However, it does not state permissions needed, reversibility, or what happens on failure. For a mutation tool, this is a moderate level of transparency.

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 well-structured with a clear opening sentence, parameter breakdown, and a compact example. The example is lengthy but necessary for explaining the schema_json format. Every part serves a purpose, though the overall length is above minimal.

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 the essential aspects of the create operation, including the target page, title, and schema structure. It does not mention return values, but an output schema is present, so that gap is acceptable. Missing prerequisites like page existence or permissions are not stated, but the description is fairly complete given its complexity.

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 provides no descriptions for its parameters, so the description must compensate. It does so thoroughly by explaining each parameter (parent_page_id, title, schema_json) and providing a detailed example for schema_json, including property types and structure. This adds significant meaning beyond the schema.

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 'Create a new Notion database under a page,' which is a specific verb and resource. It distinguishes this from sibling tools like notion_update_database (updating existing) and notion_query_database (querying) by focusing on creation. The scope of where the database is created is also specified.

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 context of use is clear: this tool creates a database and places it under a specified page. While it doesn't explicitly mention alternatives or exclusions, the description provides enough context for an agent to know when to select this tool over siblings (e.g., not for updating or querying). The 'under a page' detail adds important usage context.

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