Update Rows in Sheet

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

Annotations indicate this is a write operation (readOnlyHint=false). The description adds behavioral details: partial updates, lock/unlock, hierarchy changes, and return of updated data with new version. It does not contradict annotations.

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?

Concise: two sentences plus parameter list. Front-loaded with purpose. Each sentence adds value.

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?

No output schema, so description appropriately includes return info. Covers core behavior and parameters. Could mention required permissions or concurrency, but sufficient for typical use.

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 has descriptions for sheet_id and row_id only (50% coverage). The description's Args section explains each parameter's role, including hidden details like cells structure, locked and expanded options. However, it misses the 'formula' field in cells (present in schema). Overall adds significant value.

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 'Update one or more existing rows' with the resource 'in a Smartsheet sheet'. This verb+resource pattern distinguishes it from sibling tools like add_rows and delete_rows.

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 partial update behavior ('Only provided cells are updated') implying when to use (updating specific fields) and not (full replacement). It does not explicitly contrast with alternative tools (e.g., add_rows), but context is sufficient.

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