Manage Object Schema Columns

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

Annotations are neutral, but the description adds important behavior: changes propagate to all boards, create requires type/title, update requires column_id, and opt_out_by_default controls auto-adding. No contradictions with annotations.

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 concise with no wasted words. It starts with the main purpose, then explains both actions with clear, actionable sentences.

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?

Covers the main points: two modes, prerequisite, propagation, and key parameters. While it could mention error handling or limitations, it is sufficient for the complexity level.

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%, so baseline is 3. The description adds value beyond schema by explaining required fields for each action and the meaning of opt_out_by_default, plus the prerequisite call.

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 it creates or updates columns on an account-level object schema, specifying the resource and scope. It distinguishes from siblings like create_column by focusing on schema-level management with propagation to all boards.

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?

Provides usage guidance by differentiating create vs update and mentioning a prerequisite call to get_column_type_info. However, it does not explicitly compare to sibling tools like create_column or update_column, relying on the 'account-level' context to imply distinction.

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