append_csv_to_dataset

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

No annotations provided, so description carries full burden. Discloses parsing of CSV, appending entities, duplicate skipping, and file size/type constraints. Lacks explicit statement about mutation or error behavior, but overall adequate for the operation.

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?

Two concise paragraphs: first sentence states purpose, second provides essential details. No redundant information. Every sentence serves a purpose.

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?

Covers main usage aspects: required columns, duplicate handling, alternative tool. Output schema exists to cover return values. Minor gaps (e.g., what if dataset missing, malformed CSV) not critical for typical use.

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% so baseline is 3. Description adds significant value: explains file parameter format (raw CSV or base64, 10 MB cap, no server paths), clarifies api_key optionality with header/env var fallback, and reinforces dataset_id as required. Exceeds baseline.

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 verb 'append' and resource 'entities from a CSV file to an existing dataset'. It distinguishes from sibling tool 'create_dataset_from_csv' by explicitly directing users to use that alternative for creating new datasets.

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?

Provides explicit when-to-use (append to existing dataset) and when-not-to (creating new dataset) with a reference to the sibling tool. Offers concrete guidance on CSV format: required 'name' column, optional 'domain' or 'description', and duplicate row handling.

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