rekordbox_sync

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that backup is created for import operations, which is a useful safety behavior, but it omits other critical traits such as whether export overwrites files, what side effects occur on the Rekordbox database, or what the return values look like. This is insufficient for a tool that performs mutations.

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 two sentences long, front-loaded with the primary purpose, and contains no fluff. Every word earns its place, and the action values are clearly separated. This is a model of 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?

The tool has moderate complexity with three parameters and no output schema. The description provides the core function but lacks details on parameter formats, backup behavior specifics, and how this tool relates to the dedicated XML import/export siblings. It is not complete enough for an agent to invoke correctly without further assumptions.

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 compensate. It does explain the 'action' parameter values ('import' or 'export') with additional context, but it does not explain the 'source' or 'destination' parameters at all. Given that source and destination are essential for the action, this is a significant gap.

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 tool imports from or exports to Rekordbox, with specific action values ('import' from XML or DB, 'export' to XML). It uses a specific verb and resource, making the purpose unambiguous. It does not explicitly differentiate from sibling tools like rekordbox_importXml or rekordbox_exportXml, so it stops short of a 5.

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?

There is no guidance on when to use this tool vs. the dedicated rekordbox_importXml and rekordbox_exportXml tools. The description does not mention any exclusions or alternatives, leaving the agent to guess which import/export tool is appropriate.

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