set_column_visibility

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals that hidden columns still work in DAX and relationships – a key behavioral trait. It does not mention other side effects or prerequisites, but for a simple toggle this is valuable transparency.

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 action, the second adds critical context and a use case. Every word earns its place – no fluff, no 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?

For a simple toggle tool, the description covers purpose, key behavior, and intended use. It omits prerequisites or error handling, but these are less critical given the tool's simplicity and the presence of a sessionId common to the suite. The output is self-contained enough for an agent to select and invoke correctly.

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 0%, so the description should compensate. It gives indirect meaning to the 'hidden' parameter via 'hide or show' and the behavior note, but does not explicitly explain table, column, or sessionId. The parameter names are fairly self-explanatory, but the description adds little beyond what the schema already reveals.

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 'Hide or show a column in the field list' – a specific verb, resource, and scope. It distinguishes itself from siblings like set_column_flags or set_visual_visibility by focusing on field list visibility, and adds the important nuance that hidden columns still work in DAX and relationships.

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 provides usage context with 'use to hide keys/sort columns' and clarifies that hidden columns remain functional, which guides when to hide rather than delete. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to decide when to use this tool.

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