set_columns

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

There are no annotations to carry the behavioral burden. The description only states that it sets the layout, but does not disclose whether existing section column settings are overwritten, what values are valid, whether a cursor position or selection is required, or what side effects occur. For a mutation tool, this is a significant gap.

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 clean sentence with no filler and the key information front-loaded. It is appropriately short, though it is concise partly because it omits useful detail.

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?

With five parameters, one required, no annotations, and 0% schema coverage, the description is too thin to fully support correct invocation. An output schema exists, but it cannot compensate for missing usage guidance, parameter semantics, or behavioral context.

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% and the description does not explain count, gap, column_type, or line_separator. The phrase 'multi-column layout' provides some context, and parameter names are guessable, but the description adds little explicit semantic value beyond the schema itself.

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?

States a specific action ('Set') and resource ('multi-column layout for current section'), which is clear and legible. It does not explicitly distinguish itself from broad sibling tools like set_section_definition, so it falls short of a 5.

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 identifies the target ('current section') but provides no guidance on when to choose this tool over related siblings or when to use set_section_definition instead. No exclusions, prerequisites, or alternative routing are given.

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