roboflow_get_version_generation_status

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

No annotations are provided, so the description carries the full burden. It only states the action but does not disclose whether the operation is read-only, any authentication requirements, rate limits, or side effects. The word 'Poll' implies non-destructive querying, but this is not explicit.

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?

The description is a single sentence, making it concise. However, it sacrifices necessary detail. It is not verbose but falls short of providing adequate information for an agent to use the tool correctly.

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 that an output schema exists, the return value expectations are covered. However, the tool is part of an async workflow and lacks context about prerequisites (e.g., needing a version in generation state) and the optional 'dry_run' parameter. For a polling tool, more explanation of the flow would be helpful.

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?

The input schema has zero description coverage for any of the four parameters. The tool description does not add any meaning beyond the parameter names and types. For example, it does not explain what 'project' or 'version' specifically refer to, or the role of 'dry_run'. This severely limits the agent's ability to correctly fill parameters.

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 that the tool polls the async generation state of a version. It uses a specific verb 'Poll' and identifies the resource, distinguishing it from sibling tools like 'get_version' which likely fetch version metadata. However, it could be more explicit about the context of generation.

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 no guidance on when to use this tool versus alternatives, such as after triggering generation with 'create_version' or when to check status. No exclusions or context for use are given.

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