append_rows

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions 'validated' and 'new output file' but does not explain whether the tool modifies existing files (overwrite behavior), what validation entails, or if it is safe/read-only. The ambiguity about output file creation and overwriting is significant.

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 sentence, which is concise but not optimally structured. It front-loads 'Append validated rows' but lacks sufficient detail to be valuable. Every word should earn its place, and here the phrase 'by default' adds little clarity.

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 tool's complexity (8 params, an output schema, sibling variety) and zero annotations/param descriptions, the description is severely incomplete. It omits return value info, side effects, error conditions, and validation specifics, leaving the agent with insufficient context.

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?

The input schema has 8 parameters with 0% description coverage, yet the description adds no meaning to any parameter. It does not mention path, rows, dry_run, options, overwrite, output_file, column_types, or spreadsheet_formula_policy, leaving the agent to infer solely from names and types.

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 states 'Append validated rows to a new output file by default.' It identifies a verb and resource but is vague about what 'append' means compared to siblings like 'update_rows' or 'create_csv'. The phrase 'validated' suggests validation occurs but is not explained, and 'by default' hints at configurable behavior without clarity.

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?

No explicit guidance on when to use this tool versus alternatives. Siblings such as 'create_csv', 'update_rows', and 'delete_rows' exist, but the description does not distinguish use cases, prerequisites, or context for append vs. update or create.

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