convert_line_break_to_text

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It specifies the replacement behavior and return value, but does not disclose whether the operation is destructive, what happens if no line breaks are found, or any side effects on the file. The disclosure is adequate but not rich.

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, front-loaded sentence with no redundant words. It efficiently communicates the core action and return value, making it easy to parse.

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 4 parameters and no annotations, the description should provide more context about required inputs and optional behaviors. It covers the main function but omits details about parameters, prerequisites, and typical use cases. An output schema exists, which helps, but the description alone is not fully complete.

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 mentions 'replacement text string' (matching target_text) and 'worksheet range' (ambiguous for _range and worksheet), but does not explain file_token or the roles of optional parameters. The description provides insufficient parameter semantics.

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 the tool's function: it replaces line break characters (\n, \r\n, \r) with a specified replacement text in a worksheet range. This specific verb+resource+scope distinguishes it from sibling tools like remove_all_line_breaks or remove_extra_line_breaks.

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 explains what the tool does but does not explicitly state when to use it relative to alternatives. There is no mention of scenarios or exclusions, leaving the usage context implied rather than explicitly guided.

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