notion_update_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 explains property schema operations in detail (add, remove, rename, change type, add options) and that empty title/description keeps current values. However, it does not disclose potentially destructive effects such as data loss when removing a property or changing its type, which 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?

The description is appropriately sized for the complexity, opening with a one-line summary and using structured bullet examples for property changes. Every line adds value, and the formatting makes it easy to parse.

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 prerequisites, parameter semantics, and multiple operation types with examples. It does not explain return values, but an output schema exists, so that burden is reduced. The main gap is the absence of warnings about irreversible or destructive changes, which is important for an update 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?

Despite 0% schema description coverage, the description fully documents all four parameters inline. It provides detailed syntax and concrete JSON examples for properties_json, covering add, remove, rename, type change, and select options. This far exceeds what the bare schema offers.

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 starts with a specific verb and resource: 'Update a Notion database's title, description, or property schema.' This clearly distinguishes it from sibling tools like notion_update_page, notion_update_block, and notion_create_database. The scope is unambiguous.

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 explicitly instructs to 'Use notion_describe_database first to see current schema,' providing a clear prerequisite. It also states that multiple changes can be combined. While it doesn't name alternatives, the database-specific context makes the intended use apparent.

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