dataset_upload_folder

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

Annotations provide no behavioral hints beyond non-read-only, non-idempotent, non-destructive. Description adds no further context about side effects (e.g., zip disposal, ingest failure handling, or permission requirements). The description carries full burden but is minimal.

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?

Single sentence with clear verb-object structure. No redundancy, front-loaded with key action and resource. Every part earns its place.

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 3 parameters, no output schema, and no nested objects, the description covers the core purpose but omits details about optional parameter targetSplit and the ingest process. It is minimally adequate but lacks completeness for full understanding.

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 67% (2 of 3 params have descriptions). The description does not add parameter-specific details beyond the schema; it only mentions 'local image folder' and 'existing dataset' but not the parameters directly. Baseline 3 is appropriate.

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?

Description clearly states the verb 'Upload' and resource 'local image folder', specifying the action of zipping and starting ingest for an existing dataset. This distinguishes it from siblings like dataset_upload_file and dataset_upload_video which handle single files or videos.

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 versus alternatives like dataset_upload_file or dataset_upload_video. The description implies it's for folders but does not explicitly state exclusions or context for selection.

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