wdata_upload_and_import

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

No annotations exist, so the description bears full burden. It discloses the multi-step process, error surfacing, system column addition, and 409 duplicate behavior. It lacks explicit destructive hint but implies mutation.

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 sentences, front-loaded with purpose, no fluff. Every sentence adds value.

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 behaviors (upload, import, poll, error handling, duplicate filename), but lacks detail on timeout and what 'settled' means. Mostly complete for a complex 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?

Schema coverage is 0%, so description must compensate. It only implicitly describes 'file_path' via file types listed; 'table_id', 'delimiter', and 'timeout' are unexplained. This is insufficient for a 4-parameter tool.

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 starts with 'WRITE. Upload a local .csv/.tsv/.json (or .zip of one) into a Wdata table and import it', clearly stating the action and resource. It specifies file types and distinguishes from other tools like wdata_run_sql.

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?

It notes that this tool handles upload+import+poll in one call, contrasts with 'upload alone does NOT import', and mentions error handling and duplicate filename behavior. While it doesn't explicitly name alternatives, it provides clear context for when to use this tool.

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