show_or_hide_all_columns

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

The description does not add behavioral context beyond what annotations already provide. Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, which adequately convey the safety profile. The description merely restates the action, adding no extra details about side effects, permissions, or behavior.

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 three sentences long, front-loaded with the main action, and every sentence serves a purpose: function, usage, alternatives. No extraneous 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?

Given the tool's simplicity (4 parameters, 3 required, no output schema) and the presence of detailed annotations and sibling comparisons, the description is fully complete. It explains what the tool does, when to use it, and how it differs from similar tools.

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 coverage is 100% as all four parameters have descriptions in the schema. The tool description itself adds no additional meaning beyond the schema's parameter descriptions. With high coverage, baseline score of 3 is appropriate.

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 uses a specific verb+resource: 'Show or hide every column in a view in one call.' It clearly distinguishes from sibling tools set_view_columns and show_or_hide_view_columns by stating the scope (all columns vs specific subset or selective toggles).

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 explicitly states when to use this tool ('when you want a clean all-visible or all-hidden baseline') and provides clear alternatives with specific tool names: 'Use set_view_columns when you want to show a specific subset... Use show_or_hide_view_columns for selective per-column toggles.'

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