build_dataset

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 explicitly discloses the critical side effect: building a dataset will stop the crawler, de-register it from the network, and prevent further data collection. It also sets expectations by describing the 10-step build progress.

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 well-structured and front-loaded: purpose, usage trigger, warning, parameter list, return values, and example. Every section adds necessary value, and the critical de-registration warning is placed prominently.

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?

For a 4-parameter mutation tool with no annotations, this description is complete. It explains when to use the tool, how to obtain the required parameter, what side effects to expect, what will be returned, and provides a runnable example. An agent has enough information to invoke the tool correctly and decide whether it is safe to proceed.

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 description coverage is 0%, so the description must document all parameters, and it fully does. It defines crawler_id, max_rows, email, and redirect_url with their types, defaults, and purposes, and even tells the agent to source crawler_id from get_gravity_task_status's 'crawler_ids' field. The example further clarifies usage.

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 states a specific action and resource: 'Build a dataset from collected data before the 7-day task completion.' It clearly differentiates this from sibling tools like get_dataset_status or cancel_dataset, and the purpose is immediately understandable.

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 explicitly says when to use the tool: 'Use this when you have enough data and don't want to wait for the full collection period.' It does not name a specific alternative tool or state explicit when-not conditions, but the timing guidance and the warning about stopping the crawler provide solid usage context.

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