Add Rows to Sheet

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

Annotations indicate readOnly=false, consistent with the mutation behavior described. The description discloses that the tool returns newly created row IDs and updated sheet version. It does not contradict annotations. Additional details like idempotency (false) or potential failure conditions (e.g., sheet locked) are missing, but the essential behavior is transparent.

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 succinct: one sentence for the core purpose followed by a bulleted args list. Every sentence earns its place, with no fluff. The structure is front-loaded with the main action, and the args are clearly separated, aiding quick comprehension.

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 the complexity (2 parameters, one a nested array), the description adequately covers the purpose, parameter semantics, and return value. It does not include error handling or rate limits, but for a mutation tool with well-documented parameters, it provides enough context for correct invocation.

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?

Input schema covers 100% of parameters, providing a baseline of 3. The description adds significant value beyond the schema: it explains the purpose of positioning parameters (to_top, to_bottom, parent_id, sibling_id) and clarifies that cells are columnId/value pairs. It also describes the structure of row objects in the args list, making the tool more intuitive.

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 'Add one or more rows to a Smartsheet sheet.' with a specific verb (add) and resource (rows to a sheet). It distinguishes from sibling tools like update_rows and delete_rows by focusing on addition. The description also provides details about positioning, making the purpose unambiguous.

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 that rows can be positioned at top, bottom, or relative to parent/sibling rows for hierarchical structures. It implies usage for adding new rows, but does not explicitly state when to not use it (e.g., for updates). However, the context from sibling tool names provides differentiation, so the guidance is clear but not exhaustive.

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