Add Database Row

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

With no annotations, the description carries the full burden. It discloses that title column text is stored on the row paragraph block and that select columns auto-create options by label. However, it does not mention side effects, authorization requirements, error handling, or what happens if columns are missing.

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?

Three concise sentences with no waste. The first sentence states the main purpose, followed by two sentences adding specific behavioral details. Information is front-loaded and each sentence earns its place.

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 tool has 5 parameters, a nested object, and no output schema, the description covers key aspects: cell mapping, title storage, select auto-creation, and linked doc linking. It lacks mention of return values or error conditions, but overall provides sufficient context for correct invocation.

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 that cells can be mapped by column name or ID, and that for select columns, the display label is passed (auto-creating options). It also clarifies the linkedDocId parameter's purpose beyond the schema.

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 adds a row to an AFFiNE database block, specifying the verb ('add') and resource ('row to a database block'). It distinguishes from siblings like add_database_column (adds columns) and update_database_row (modifies rows) by focusing on row creation.

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?

Usage is implied: use this tool to add a new row. However, there is no explicit guidance on when not to use it (e.g., for updates, use update_database_row) or mention of alternatives. The description lacks contextual hints for choosing between siblings.

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