spreadsheet_append_rows

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

No annotations are provided, so the description must cover behavior. It states that 'confirm=true' executes the operation, implying a dry-run when false, which is useful. However, it does not disclose whether the operation is reversible, any row width limitations, or authorization needs. More detail would improve transparency.

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 two sentences long with no redundant information. It is front-loaded with the core action and follows with key parameter guidance, making it easy to parse quickly.

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?

While the description covers the basic usage pattern, it lacks details about return values (e.g., success status, appended row count), error handling, or edge cases like mismatched column widths. Given the tool has 6 parameters and no output schema, more information would be beneficial for complete understanding.

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 coverage is high (83%), but the description adds value by explaining the optional use of 'file_id' or 'name' and the role of 'confirm'. This goes beyond the schema definitions, helping an agent understand parameter relationships.

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 ('Append rows') and resource ('Synology Spreadsheet sheet'), clearly distinguishing it from siblings like 'spreadsheet_write_cells' which overwrites cells. It is immediately clear what the tool does.

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 advises using either 'file_id' or 'name' and setting 'confirm=true' to execute, providing basic guidance. However, it does not explicitly differentiate when to use this tool instead of alternatives like 'spreadsheet_write_cells' or 'spreadsheet_batch_update', which would be helpful.

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