set_view_cell_wrap

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

The description discloses the toggle action and the two states (wrap vs truncate), which aligns with the idempotentHint annotation. It adds behavioral context beyond the annotations by clarifying the visual effect on cell values. However, it does not elaborate on any side effects or prerequisites.

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, concise sentence that immediately conveys the purpose. It is front-loaded with the verb and uses clear terminology ('multi-line', 'ellipsis'). There is no wasted text.

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 adequately explains what the tool does given its simplicity. It does not require an output schema explanation. However, it could explicitly state that it applies to a specific view (implied by parameters but not the description).

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 100%, so the baseline is 3. The description does not add additional meaning beyond the schema; it only restates the boolean parameter's effect. The parameters are self-explanatory from the schema.

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 ('Toggle') and clearly identifies the resource ('long cell values wrap...or truncate'). It directly states the effect on the view's display behavior, which distinguishes it from sibling tools like 'set_view_columns' or 'set_view_color_config'.

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 does not explicitly state when to use this tool or when not to use it. It provides no comparison to alternative tools, such as those for setting column widths or line height. The usage context is implied by the toggle behavior, but no guidance is given.

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