Add Database Row

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

The description adds meaningful context beyond annotations: select columns auto-create options by label, and title column text is stored on the row paragraph block. Annotations indicate readOnlyHint=false, openWorldHint=true, etc., and the description does not contradict them. No mention of error handling or row duplication behavior, but overall good.

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 focused sentences with no wasted words. Front-loaded purpose in first sentence. Efficient and to the point.

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's moderate complexity, annotations, and no output schema, the description covers main behaviors and parameter use. Could mention non-idempotent behavior (creating a new row each call) but is otherwise sufficient.

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 description coverage is 100%, so baseline is 3. The description clarifies the 'cells' map usage and behavior for select columns, adding value beyond the schema. However, it does not elaborate on other parameters like linkedDocId or workspaceId beyond what the schema already states.

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 action ('Add a row') and the resource ('AFFiNE database block'). It provides specific details about cell value mapping by column name or ID, and behavior for title and select columns, which helps distinguish from update/delete database row tools.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., update_database_row for modifications). No prerequisites like having the docId or databaseBlockId mentioned. The description implies usage for adding rows but does not set boundaries or exclusions.

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