import_rekordbox_xml

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

With no annotations, the description must carry the behavioral burden, and it does add a useful safety note ('Read-only on the XML'). But it remains silent on equally important behaviors such as whether the import merges with or replaces existing sets, duplicate handling, or what happens with invalid/unsupported files.

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?

One dense sentence conveys the source format, version, data extracted, destination concept, and safety property, with no filler. The important resource and format details are front-loaded.

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 single-parameter import tool, the description is complete enough to invoke correctly: it identifies the file source, path provenance, format constraints, and the high-level effect (importing content into sets). The absence of an output schema is slightly mitigated by the clarity of the import action, though merge/replacement semantics would make it fully complete.

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 schema covers the only parameter (path) with its own detailed description including the menu path, so schema coverage is 100% and the baseline applies. The tool description does supplement with file-format/version constraints, but it does not need to re-document the parameter.

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 names a specific verb and resource: importing a Rekordbox 'Export Collection in xml' file. It goes further by stating the file format/version, the data it extracts (BPM/key/genre, cues, playlists), and the mapping 'playlists → sets', which clearly differentiates it from sibling tools like import_history or scan_folder.

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 context for use is clearly stated: use this when the user provides a Rekordbox collection XML export, with an explicit version constraint (6.3.0+, plaintext). However, it does not explicitly mention sibling alternatives or state when not to use it, so it stops short of full usage routing.

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