Add Wiki grid columns

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

Annotations already declare destructiveHint=false and idempotentHint=false, lowering the bar, and the description adds real behavior: the default append position when no index is supplied, and the fact that a new grid revision is produced. It still omits the revision/concurrency conflict story that matters for a non-idempotent mutation.

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?

Front-loaded with the action and placement default, then the required-column rule, then the return value. Slightly padded by echoing the type enum ('string, number, select, staff, date, checkbox, ticket_field, …') that the schema already enumerates.

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 required shape, positioning, and the return value (the new revision), which is useful since there is no output schema. For a nested-object mutation it is nearly complete, missing only error/conflict behavior around the revision field.

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% and every field, including nested column properties, is documented in the schema. The description only restates the required title/type pair and cites select_options and ticket_field as examples, adding no syntax or format detail beyond the structured data, so the baseline 3 applies.

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?

States a specific verb and resource ('Add columns to a grid') plus placement semantics ('at a position (default: append after the last column)'), which implicitly separates it from wiki_grids_columns_move and wiki_grids_columns_update. It does not explicitly name any sibling, so it stops short of a 5.

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?

Usage is only implied by the verb: an agent can infer 'use this to add new columns', but the description never states when to reach for this versus wiki_grids_columns_update (modify existing), wiki_grids_columns_suggest, or wiki_grids_columns_move. No prerequisites or exclusion conditions are given.

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