text_to_columns

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

No annotations are present, so the description must fully disclose behavior. It does not explain whether the original column is replaced or preserved, what delimiter types are supported (beyond schema defaults), or any side effects like data loss. This is insufficient for safe invocation.

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 single sentence is concise but lacks essential detail. It is well-structured and front-loaded with purpose, but it is too brief to be considered efficient—it sacrifices completeness for brevity.

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 no output schema and only two required parameters (spreadsheet_id, source_range), the description fails to explain the default delimiter behavior, error conditions, or the resulting range location. Completeness is inadequate for a tool with multiple optional parameters.

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 property descriptions have 0% coverage, so the description should add meaning to parameters. However, it only mentions 'single-column range', omitting details about the delimiter, delimiter_type, and how source_range is interpreted. The description adds no value beyond parameter names.

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 'Split a single-column range into multiple columns' uses a specific verb (split) and resource (single-column range) and clearly distinguishes the tool's purpose from siblings like paste_delimited_data, which imports external delimited data rather than splitting an existing column.

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 on when to use this tool versus alternatives such as paste_delimited_data or sort_range. The description lacks context for preferred use cases or limitations, leaving the agent to infer usage from the name alone.

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