rekordbox_importXml

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

The only disclosed behavior is that a backup is created before loading, which is useful but incomplete. The description does not state whether the import replaces or merges the existing library, nor what happens on failure. With no annotations, this is a significant gap for a mutation tool.

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?

Two short sentences with no filler; the primary action is stated first and the backup detail is a useful addition without redundancy.

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 description lacks critical details about the import's effect on existing data, return values, and error handling, which is especially important given the absence of annotations and output schema.

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 description implies that xmlPath is the path to the Rekordbox XML file, but it does not explicitly clarify the parameter's format, required extension, or whether it accepts a local path or URL. With 0% schema coverage, this is partial compensation.

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 a library from a Rekordbox XML file, using a specific verb and resource. The source format distinguishes it from sibling tools like library_load or rekordbox_exportXml.

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 library_load or rekordbox_exportXml. It does not mention prerequisites, overwrite/merge behavior, or when this tool is preferred.

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