roboflow_create_version

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

Given no annotations, the description discloses async behavior, quota destruction, required environmental mode, and polling expectation. It does not cover failure modes or rate limits.

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 concise sentences with front-loaded core action. Efficient but could benefit from structured format for requirements.

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?

Missing key details: return structure for polling, error handling, parameter descriptions, and full lifecycle. Async tool with 7 parameters requires more context than provided.

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?

With 0% schema description coverage, the description only hints at the 'confirm' parameter needing 'yes'. No explanation for project, workspace, preprocessing, augmentation, train_test_split, or dry_run, leaving the agent to guess formats and valid values.

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 it kicks off async version generation (quota-heavy) and distinguishes from siblings by mentioning polling of roboflow_get_version_generation_status. However, the verb 'kick off' is informal and could be more specific.

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?

The description provides usage constraints (requires confirm='yes', ROBOFLOW_MCP_MODE=curate or full) and a polling hint, but lacks explicit when-to-use vs alternatives or when not to use.

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