get_column_formatting

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

There are no annotations, so the description carries full responsibility. It only states the operation's purpose, not any behavioral traits such as whether it is read-only, what it returns if formatting is unset, or any permission requirements. The word 'Get' implies a safe read, but no further disclosure is made.

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 a single, clear sentence with no verbose wording. It is front-loaded and to the point. However, it is arguably too terse, omitting any parameter or usage details, but that is more an issue of other dimensions. For clarity and brevity, it scores well.

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 lack of annotations and output schema, the description should at least mention the required parameters and the nature of the returned JSON formatting. It provides only the most basic statement of purpose, leaving the agent without enough context to know how to invoke the tool correctly or understand the output.

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?

The schema has zero description coverage and no descriptions for listId or columnId. The description adds no information about these required parameters or how to identify the column/list. The parameters are left entirely to their names, which is inadequate for a tool that requires both parameters.

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 the specific verb 'Get' and clearly identifies the resource as JSON formatting for a SharePoint list column. It distinguishes from sibling tools like get_view_formatting by specifying 'column' rather than 'view', and from preview/apply update tools by using 'get' rather than 'preview/apply'. However, it doesn't explicitly say it retrieves existing formatting, though that is implied.

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?

No guidance is provided about when to use this tool versus alternatives. It doesn't mention that this is the read-only counterpart to preview_column_formatting_update/apply_column_formatting_update, nor does it suggest using get_view_formatting for view-level formatting. The description gives no context or prerequisites.

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