Add Columns to Sheet

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

The description discloses supported column types, required options for picklist, and the return value (created column definitions with assigned IDs). Since annotations are all false (no readOnly, no destructive hints), the description adds useful behavioral context beyond 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 a one-line summary, a bullet list of types, and a structured args section. Every sentence adds value without 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?

The description covers the purpose, parameter details, and return value. However, it lacks information about error conditions, permissions required, or whether the sheet must exist. Still, for a straightforward mutation tool, it is nearly complete.

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?

Despite the context indicating 0% schema description coverage, the description provides detailed semantics for the 'columns' parameter, including optional fields like index, options, and width, and explains the meaning of index (0-based position, appends if omitted). This adds significant value over the schema alone.

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 one or more new columns to a Smartsheet sheet' using a specific verb and resource. This distinguishes it from siblings like smartsheet_get_columns (reading) and smartsheet_add_rows (adding rows).

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 guidance on when to use this tool versus alternatives like smartsheet_update_rows to modify columns. The description lists supported column types but does not specify use cases or exclusions.

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