notion_database

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

No annotations are provided, so the description carries the full burden and does not meet it. It never discloses that update_database mutates existing schema (potentially destructive to property definitions), that create_database requires a parent, or that query_database is a read-only paginated call. Only the bare word 'update' hints at mutation.

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?

One short sentence, front-loaded and free of padding, so it is concise. The problem is under-specification rather than verbosity — the space saved is not spent on anything useful.

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?

This is a three-action union tool with a large nested schema and no annotations or output schema. The description should route the agent between actions and between this tool and notion_pages/notion_blocks, but it gives only a parenthetical verb list, leaving an agent unable to confidently choose an action.

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 coverage is 100%, and the payload union itself documents each action and its nested params, so the schema does the heavy lifting. The description merely repeats the action list already present in the payload description, adding no semantic value about action selection or parameter interplay.

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 names the resource (database) and three verbs (create, query, update), which does separate it from siblings like notion_pages and notion_blocks. But 'various database operations' is a vague umbrella that doesn't say what a database operation actually accomplishes or which action maps to which intent.

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 when-to-use guidance at all: no statement of when to call this versus notion_pages, no indication of when to pick create vs query vs update, and no prerequisites such as needing a parent page or existing database_id.

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