add_column

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the default view behavior which is useful, but doesn't address important aspects like required permissions, whether this is a destructive/mutating operation, error conditions, or what happens if the column already exists. For a mutation tool with zero annotation coverage, this is insufficient.

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 perfectly concise - a single sentence that communicates the core functionality and key behavioral detail (default view behavior). Every word earns its place with zero waste or redundancy.

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?

For a complex mutation tool with 3 parameters (including a deeply nested object), no annotations, and no output schema, the description is inadequate. It doesn't address the tool's complexity, expected outcomes, error conditions, or the rich parameter structure that requires significant guidance for proper use.

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?

With only 33% schema description coverage, the description must compensate but adds minimal parameter context. It mentions the addToDefaultView parameter behavior but doesn't explain the complex 'column' object structure or the 'listName' parameter. The description doesn't provide meaningful semantic context beyond what's already in the sparse schema descriptions.

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 specific action ('add a new column') and target resource ('to an existing list or library'), distinguishing it from sibling tools like create_list or update_column. It provides a complete verb+resource statement that is unambiguous.

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 context by mentioning 'existing list or library' and the default view behavior, but doesn't explicitly state when to use this tool versus alternatives like update_column or create_list. No explicit exclusions or prerequisites are provided.

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