Update Database Row

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

No annotations are provided, so the description must disclose all behavioral traits. It explains that 'title' can be used to update the Kanban row title, but does not mention side effects, idempotency, permissions required, or error conditions. For a mutation tool, this is insufficient transparency.

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?

Two sentences, no wasted words. The first sentence states the primary action, the second adds a crucial nuance about the 'title' parameter. Front-loaded and efficient.

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?

Given the number of parameters (7) and nested objects, and no output schema, the description is somewhat complete but lacks information about return values or possible errors. It does not explain the response format or state what happens if the row does not exist, which are gaps for an agent.

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% (baseline 3). The description adds value by explaining the special 'title' key for updating the Kanban row title, which is not obvious from the schema alone. It also implies the mapping between column names/IDs and values, though it does not elaborate on createOption or linkedDocId beyond their schema descriptions.

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 clearly states the tool updates an existing AFFiNE database row and supports batch operations on multiple cells. It distinguishes itself from sibling tools like add_database_row and delete_database_row by focusing on updates, but does not explicitly contrast with update_database_cell (single cell update) which is a sibling.

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 implies use for batch updating multiple cells but does not provide explicit guidance on when to use this tool vs sibling tools like update_database_cell or add_database_row. No when-not-to-use or alternative recommendations are given.

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