sync_tracking_dataset

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

The description implies a non-destructive read operation (downloading), but provides no details on authentication, rate limits, overwrite behavior, or the impact on the source. With no annotations, the tool's behavioral implications are vague.

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 one concise sentence, but its brevity sacrifices necessary detail. It is front-loaded with the main action, but could be expanded minimally to cover key aspects without losing conciseness.

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 6 parameters, no schema descriptions, and no output schema shown, the description is severely incomplete. It fails to explain the purpose of each parameter or the tool's overall workflow, leaving the agent without sufficient context.

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%, and the tool description does not explain any of the 6 parameters (target, output_folder, login, http_port, name_type, dataset_path). The agent receives no guidance on required vs optional fields or their meanings.

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 the verb 'download' and the resource 'recorded Steam Frame tracking dataset directory', specifying the action and target. It distinguishes this tool from siblings like 'tracking_dataset_analyze' or 'sync_logs' by focusing on downloading a directory.

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 is provided on when to use this tool versus alternatives, such as when to sync logs or analyze datasets. There is no context on prerequisites, required device state, or common scenarios.

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