import_tracks

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

The description explicitly warns 'This modifies your rekordbox database' and includes a caution marker, which adds behavioral context beyond the annotations. It also discloses that tracks are imported unanalyzed and that rekordbox must be closed—additional traits not present in the annotations. This is strong transparency.

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 with a clear overview, caution, process notes, tip, and documented parameters/returns. It is somewhat long but every section adds value. The front-loaded purpose and caution make it efficient, though the tip and returns could be condensed.

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 the tool's complexity (batch import, directory recursion, extensions, database modification), the description covers prerequisites (rekordbox closed), post-import behavior (unanalyzed tracks, need to analyze), return summary, and a follow-up suggestion. The output schema covers return details, so the description is complete for an agent to decide and invoke.

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?

Despite zero schema description coverage, the description's Args section explains each parameter in plain terms: paths (file/directory paths), recursive (descend into subdirectories), auto_tag (read ID3 tags via mutagen), and extensions (restrict scans). This fully compensates for the schema's lack of descriptive text.

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 opens with a specific verb and resource: 'Batch-import audio files and/or directories into the rekordbox library.' It clearly distinguishes from the singular sibling tool import_track by emphasizing batch import, and clarifies the target system (rekordbox library).

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 provides clear context: it's a batch import with a prerequisite (rekordbox must be closed) and a follow-up action (run Analyze Tracks). It also suggests a follow-up tool. However, it does not explicitly say when to use this over import_track or when not to use it, so it lacks explicit exclusions or alternative guidance.

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