set_column_group_sort

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

No annotations are provided, so the description carries the full burden. It mentions the refusal behavior for row-axis groups, which is good. However, it does not disclose other behavioral traits such as whether the operation is destructive (though 'replace' implies it), permissions needed, or error responses. The description provides some transparency but is not thorough.

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, directly stating the action and the key constraint. No extraneous words, front-loaded with the main purpose.

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 that there are 4 required parameters with no schema descriptions, no output schema, and no annotations, the description should provide more context about parameter roles and operation results. It omits explanations for 'path' and 'tablix_name', and does not mention if editing transactions are needed, leaving gaps for correct invocation.

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 must compensate. It only implicitly mentions 'group_name' and 'sort_expressions', but does not explain 'path' or 'tablix_name'. The description adds minimal meaning beyond parameter names, failing to compensate for the lack of schema descriptions.

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 that the tool replaces sort expressions for a column-axis group. It differentiates from the sibling 'set_group_sort' by specifying that it refuses if the group is on the row axis, providing a clear verb and resource.

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 (for column-axis groups) and when not to (if group_name is on row axis, use set_group_sort instead). This provides excellent guidance on alternatives.

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