notion_create_database

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

No annotations are supplied, so the description carries the full disclosure burden. It reveals nothing about required permissions, whether the parent must be a page, what the created database contains, or any side effects of the write operation.

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?

Three words with zero waste and a front-loaded verb, but the size reflects under-specification rather than disciplined conciseness. It neither buries nor spends words well because it says almost nothing.

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 nested object parameters, three required fields, no annotations, and no output schema, the description is wholly inadequate. An agent cannot determine prerequisites, permission needs, or the shape of a successful result.

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 all five parameters (parent, title, properties, icon, cover) are already documented in the schema. The description adds no parameter meaning beyond the baseline, which is acceptable given the high coverage.

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 ('Create a new database'), so the purpose is legible. However, it merely rewords the tool name (notion_create_database) and offers no differentiation from sibling database tools like notion_create_database_from_template or notion_duplicate_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?

There is no indication of when to use this tool versus notion_create_database_from_template or notion_duplicate_database, nor any stated prerequisites. No context or exclusions are provided.

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