remove_tablix_column

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

The description discloses the destructive behavior (drops column, member only if leaf, cells from all rows) and error conditions. It does not mention side effects, permissions, or transaction context, but given no annotations, transparency is above average.

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?

Three sentences efficiently explain the action, details, and error condition. No fluff. Each sentence adds value, and the key verb is front-loaded.

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?

The description covers the core operation well but omits explanation of two parameters ('path', 'tablix_name') and does not mention the need for an editing transaction (sibling tools indicate transaction management). Return value is not addressed but no output schema exists.

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 description must explain all parameters. Only 'column_name' is explained in context. 'path' and 'tablix_name' are not described, leaving the agent to infer their meaning. This is a significant gap.

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 the verb 'Remove' and the resource 'tablix column'. It specifies the exact condition (based on textbox name) and details what is removed (column, member if leaf, cells). This distinguishes it from sibling tools like remove_column_group or remove_tablix_filter.

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 implies usage when you want to remove a column identified by a textbox in its data cell, and error conditions are given. However, it does not explicitly guide when to use this tool versus alternatives (e.g., remove_column_group for groups) or mention prerequisites like an active editing transaction.

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