append_csv_to_table

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

No annotations provided, so the description must disclose behavior. It states append and existing table, but does not mention required permissions, error handling (e.g., if table doesn't exist), or whether duplicates are handled. Minimal behavioral detail.

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, concise but too brief. It front-loads the purpose but omits necessary details. Acceptable for simplicity but not optimal for completeness.

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 and no annotations, the description leaves gaps: it doesn't specify that a CSV must be uploaded beforehand, the outcome on success, or any side effects. Incomplete for a mutation tool.

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?

Only one parameter (table_id) with 0% schema description coverage. The description does not elaborate on how to obtain the table_id or any additional constraints. For a single-param tool, more semantic guidance is needed.

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 the action (Append rows from CSV upload), the target (existing table in a database), and the context (Metabase). It distinguishes from sibling tools like upload_csv or replace_table_csv.

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 guidance on when to use this tool vs alternatives (e.g., replace_table_csv). No prerequisites mentioned, such as the need for a prior CSV upload or table existence. The description lacks context for decision-making.

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