Bulk Update Rows

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

Annotations already declare destructive=true and idempotent=true, but the description adds major behavioral context: dry-run defaults on and returns current values, validation happens before writes, changed rows are snapshotted, failures are reported per row, and the entire batch can be reverted with one notion_undo.

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 dense but front-loaded: it states the core operation and its two modes immediately, then layers safety behavior and limits. Every sentence carries information useful for correct invocation.

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 complex 9-parameter mutation tool with no output schema, the description covers the important operational contract: modes, row cap, dry-run default, validation, snapshots, per-row failures, and undo. It is only slightly incomplete because a few supporting parameters are left to the schema.

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?

With schema coverage at 44%, the description compensates well for the core parameters: it explains set with where/filter, rows as [{page, set}], the 500-row cap, and dry_run behavior. It adds filter operator examples via notion_query syntax, though less common parameters such as database, data_source_name, and allow_new_options remain unexplained in the prose.

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: update many rows at once, with two distinct modes. It distinguishes bulk update from single-row siblings like notion_update_properties by naming the where/filter and rows approaches.

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 explains the two supported usage modes and recommends dry_run=true as the default confirmation step. It references notion_query for filter syntax and notion_undo for reverting, but does not explicitly state when not to use this tool versus single-row update alternatives.

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