import_history

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 explicitly states the tool is 'READ-ONLY' and 'Never writes your DJ libraries,' which is a key safety guarantee. It also notes that 'newer master.db is SQLCipher-encrypted and will be reported' (in the parameter description), disclosing a failure mode. This is strong behavioral transparency, though it does not specify whether the import appends, merges, or replaces existing data in the sets/history tables.

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, with no wasted words. It front-loads the most critical constraint ('READ-ONLY') and immediately states the resource and sources. The second sentence reinforces the safety guarantee. This is exemplary conciseness and structure.

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 tool with three optional parameters and no output schema, the description covers the core purpose and safety profile adequately. It explains what it imports, from where, and that it is read-only. However, it omits details about the impact on existing data (e.g., whether it appends or overwrites entries in sets/history) and does not describe any progress or confirmation behavior. Given the schema coverage and simplicity, this is a minor gap, but the description could be more complete for an agent to fully anticipate side effects.

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 input schema has 100% coverage, with every parameter described in the schema itself (source enum, serato_dirs, rekordbox_db). The tool description adds no additional parameter meaning beyond what the schema provides. Since the schema does the heavy lifting, the baseline of 3 is appropriate; the description does not compensate for any gaps because none exist.

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's function: 'READ-ONLY import of Rekordbox (master.db opened read-only) / Serato crates into sets/history tables.' It specifies the verb, resource, and source, and distinguishes itself by emphasizing it 'Never writes your DJ libraries.' This is precise and actionable, and it differentiates from siblings like import_rekordbox_xml by indicating it handles master.db and Serato crates rather than XML.

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 implies usage through the 'READ-ONLY' and 'Never writes' phrasing, suggesting it is safe to use without modifying source libraries. However, it does not explicitly mention when to use this over alternatives such as import_rekordbox_xml, nor does it state conditions like 'use this for master.db imports' or 'use XML for Rekordbox XML files.' The guidance is implicit rather than explicit, so it only partially fulfills this dimension.

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