format_column

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

With no annotations, the description only states the action and examples. It doesn't disclose that omitting a parameter keeps the existing value (though the schema hints this), nor any side effects or permissions. The description carries the burden but provides minimal behavioral context.

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?

One sentence with no filler, directly stating the action and illustrating valid values. Every word earns its place, and the examples are useful for parameter syntax.

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 captures the core functionality but leaves usage context and behavioral expectations unstated. Given the tool's simplicity and the many sibling tools, it's adequate but not fully helpful for an agent to decide when to choose this tool over alternatives.

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 description adds examples for formatString and dataCategory, but the required parameters (sessionId, table, column) are not explained. Schema coverage is 40%, and the description partially compensates for the optional parameters but leaves the required ones to naming conventions.

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 a specific verb ('Set') with a clear resource ('a column's format string and/or data category'), and provides concrete examples for both. It clearly communicates the tool's dual function and distinguishes it from single-purpose siblings like set_column_data_category.

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 on when to use this combined tool versus the separate set_custom_format_string or set_column_data_category tools. The description doesn't mention any conditions, prerequisites, or alternatives, leaving the agent to infer usage from the schema and sibling names.

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