update_collection_columns

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

With no annotations, the description fully discloses the critical behavioral trait: the PATCH replaces the whole schema, so omitting a column drops it. It also notes that system columns are automatically included, which is essential for predicting side effects. This exceeds the burden without 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 two sentences: the first states the purpose, the second explains the key behavior. It is front-loaded, concise, and every sentence carries essential information with no filler.

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 is complete for a two-parameter tool with no output schema. It explains the full behavioral contract—how the tool works, what gets replaced, and the consequence of omission. It also implicitly covers prerequisites by stating it reads the current schema internally. No missing critical information.

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 the schema already documents all parameters, including the 'columns' field as 'The FULL set of custom columns.' The description reinforces this by saying omitting a column drops it, but this adds minimal semantic value beyond the schema's explicit wording.

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 verb and resource: 'Add or change a collection's custom columns.' It distinguishes itself from sibling tools like create_collection, delete_collection, and update_page by targeting the specific sub-resource of custom columns.

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 for adding/changing custom columns and explains the mechanism (reads schema, PATCHes with replacements), but it does not explicitly state when to use this vs. alternatives or mention exclusions. It lacks direct guidance like 'To create a new collection, use create_collection.'

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