Remove Wiki grid columns

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes further by stating the loss is total ('every cell in them is lost') and irreversible, and by flagging the unusual DELETE-with-body transport. It stops short of stating permission/auth requirements or concurrency implications of the revision field.

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?

Roughly three lines, front-loaded with the destructive action, followed by the irreversibility, the transport quirk, and the return value. Every clause carries information.

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 destructive mutation with no output schema, it covers what is destroyed, the non-standard body transport, and what comes back (new revision). Minor gaps: no mention of auth scope, and the concurrency role of the optional revision field is left to the schema.

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% with a fully documented nested body, so the baseline is 3. The description adds real value by clarifying that slugs and revision travel in the JSON body rather than path/query, but it does not explain the meaning or optionality of revision beyond what the schema already says.

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?

Specific verb + resource: 'Delete columns from a grid by slug', which cleanly separates it from sibling row/grid operations (wiki_grids_rows_delete, wiki_grids_columns_update, wiki_grids_delete). It never names a sibling to disambiguate, but the scope is unambiguous from the text alone.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative — an agent could confuse this with wiki_grids_delete or wiki_grids_columns_update. The description only explains how to call it (body-transported slugs/revision), not when it is the right tool.

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