Add Database Column

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

The description adds no behavioral context beyond the annotations, which already indicate a non-read-only, non-destructive mutation. It does not disclose whether the operation is reversible, how it affects existing rows, or any permission requirements, leaving the agent without additional operational insight.

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 consists of two succinct sentences: the first states the primary action and target, and the second lists supported types. It is front-loaded with the core purpose and contains no wasteful or redundant content.

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 presence of an output schema, complete parameter descriptions, and annotations, the description is sufficient for understanding the tool's basic operation. It lacks details on side effects like default column values or impact on existing rows, but these are not critical given the structured data available.

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 input schema provides 100% description coverage for all seven parameters, so the baseline is 3. The tool description only reiterates the supported types already captured in the enum, adding no new semantic meaning 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 'Add a column to an existing AFFiNE database block' with a specific verb and resource. It distinguishes itself from sibling tools like add_database_row by explicitly targeting columns, and it enumerates the supported column types, reinforcing the tool's scope.

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 usage when a column needs to be added to an existing database, but it does not explicitly mention alternatives like add_database_row or provide when-not-to-use guidance. The context is clear, yet no exclusions or alternative tools are referenced.

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