set_isavailableinmdx

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

With no annotations provided, the description carries the full burden. It discloses the critical side-effect of flipping false on SortByColumn targets (invalid column ID error) and explains the memory/processing benefit. However, it does not mention any permissions, reversibility, or return behavior, leaving some gaps.

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 dense but well-structured: a clear opening, a practical rationale, a distinct GUARD note, and usage modes. It is slightly long but every sentence provides value; 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?

For a property setter with no output schema and no annotations, the description covers purpose, usage, mode selection, and a critical guard. It lacks details on error behavior, permissions, or return values, but these are less critical for a straightforward setter.

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 80%, but the description adds significant meaning beyond the schema. It explains how table/column/bulkHeuristic interact ('Pass table+column for one column; pass table alone to set a whole table; or bulkHeuristic=hiddenAndKeys'), which is not evident from the property descriptions alone.

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 opens with 'Set Column.IsAvailableInMDX', a clear verb+resource statement. It further explains the purpose (saving memory/processing) and distinguishes this from other set_* siblings by naming the specific MDX availability property.

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 (false on high-cardinality, non-attribute columns), includes a specific GUARD about SortByColumn targets that would break the sort, and describes three invocation modes (column, table, or bulkHeuristic) with clear conditions for each.

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