Add Database Row

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

The description discloses non-obvious behaviors: title column text is stored on the row paragraph block, and select columns auto-create options by label. These details complement the annotations (readOnlyHint=false, openWorldHint=true) and add transparency about side effects without contradicting any 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?

The description is three concise sentences with no wasted words. The first sentence states the core action, and the subsequent sentences add high-value details about cell mapping and edge cases.

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 nested objects and 5 parameters, the description covers key usage aspects: how to map cells, special handling of the title column, and select column behavior. An output schema exists, so return values need not be described. A slight gap is the lack of elaboration on linkedDocId, but the schema already explains that.

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?

The schema already documents all 5 parameters with descriptions, so baseline is 3. The description enriches the cells parameter by explaining that values map by column name/ID and that select column labels auto-create options, which adds meaning beyond the schema's generic definition.

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 begins with 'Add a row to an AFFiNE database block', which is a specific verb and resource. It clearly distinguishes from sibling tools like update_database_row and delete_database_row by focusing on 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?

The description provides clear how-to context but does not explicitly state when to use this tool versus alternatives such as update_database_row or read_database_cells. Usage is implied by the word 'Add' and the tool's name, but no alternative tools or exclusionary conditions are mentioned.

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