roboflow_add_reviewed_to_dataset

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

Discloses destructive nature, authentication requirement (browser cookie), random splitting at given ratios. No annotations provided, so description fully carries this burden.

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?

Concise single paragraph, front-loaded with primary action. Could be broken into bullet points for clarity, but no excess verbiage.

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?

With 8 parameters and no annotations, description covers core behavior, constraints, and key parameters. Does not detail return format (output schema exists but not referenced). Adequate for complexity.

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 0%, but description explains confirm, job_ids, train/valid/test_ratio. Missing explanations for project, workspace, dry_run. Partially compensates.

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 the verb 'add' and resource 'dataset', specifies scope 'every fully-reviewed annotation job'. Distinguishes from siblings like upload_image or add_tags.

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 context: requires confirm='yes', specific server mode, and ROBOFLOW_SESSION_COOKIE. Mentions optional job_ids restriction. No explicit when-not-to-use, but sufficient guidance.

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