append_rows

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

Discloses two important behaviors: rejects unknown columns, and response may use column keys instead of names due to API limitation. Annotations are all false (not read-only, not destructive, not idempotent, not open-world), which matches the description's write operation. No contradictions.

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?

Three short, front-loaded sentences. Each provides distinct value: purpose, constraints, and caveat. No wasted words.

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 no output schema, the description covers key behaviors (rejection, limitations) and column key note compensates. Could mention max batch size (from schema: 100 rows) or idempotency, but not critical.

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 100%, but description adds context: 'rejects unknown columns' clarifies validation behavior, and 'column name → value' hints at the format of row objects. The note about column keys further aids correct interpretation of return values.

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?

Clearly states 'Batch insert rows' with a specific verb and resource. Differentiates from siblings like 'add_row' (single row) and 'upsert_rows' (insert-or-update).

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?

Explicitly tells when not to use: cannot set link/file/image columns, directing to alternatives 'link_rows' and 'upload_file'. Implicitly distinguishes from 'add_row' for batches, but no explicit when-not for other siblings like 'update_rows'.

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