Create Database

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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, and destructive=false. The description adds useful behavior: full schema creation in one call, automatic 'Name' title property, and that notion_undo trashes the database. It does not cover permission requirements or rate limits.

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 front-loaded with the core action and remains dense with useful schema details. It is long, but the complexity of the property schema justifies most of the length; phrases like 'and more' are slightly imprecise.

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 mutation tool with no output schema and only 43% schema description coverage, the description gives solid creation semantics, default title behavior, and next-step routing. It stops short of covering permissions, return value expectations, or all parameter details.

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 only 43%, so the description must compensate. It does so substantially for the complex 'properties' parameter by enumerating property types, status groups, number formats, formulas, relations, rollups, unique ID prefixes, and the default title property behavior, though it leaves icon, cover, inline, parent, and description parameters mostly to 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 uses a specific verb and resource: 'Create a database under a page with its full schema in one call.' It also names sibling tools for adding rows and undoing the operation, so an agent can distinguish this from notion_create_page, notion_bulk_create, and notion_undo without opening 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?

It clearly routes post-creation row insertion to notion_bulk_create or notion_create_page and notes that notion_undo trashes the database. However, it does not explicitly state when not to use this tool or compare it to other database-related tools.

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