Bulk Create Rows

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

Goes well beyond the annotations by disclosing pre-write validation ('Every row is validated before anything is written'), partial-failure semantics ('Rows that fail while writing are reported; the rest stay'), and the fact that one notion_undo trashes all created rows — none of which is in readOnly/destructive/idempotent hints.

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?

Five dense sentences, each carrying distinct information, front-loaded with the core action and input modes and closing with failure/undo behavior. No repetition of the title or filler.

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 7 parameters, the description covers the essential risk surface (validation, dry_run default, partial failure, undo) and value semantics via notion_update_properties. It is slightly short on the two undocumented secondary parameters but otherwise complete enough to call safely.

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 only 14%, so the description must compensate, and it does partly: it maps rows/csv/csv_path, notes the dry_run default, and clarifies forgiving key matching and empty-cell handling. However, data_source_name and allow_new_options get no explanation at all, leaving gaps the schema cannot fill.

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?

States a specific verb and resource ('Create up to 1000 database rows') with concrete input modes (JSON objects, CSV text, CSV path), which cleanly distinguishes it from notion_create_page and notion_bulk_update.

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?

Explains the input paths and the dry_run default, and points to notion_update_properties for value semantics plus notion_undo for reversal. It does not explicitly state when to prefer this over notion_create_page or notion_bulk_update, so it stops short of full alternative routing.

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