library_load

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

There are no annotations provided, so the description carries the full burden. It discloses that a backup is created before loading and explains the default path behavior, which is valuable. However, it does not mention whether loading replaces the existing library, merges, or has other side effects, leaving gaps in 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 two sentences with no redundant information. It front-loads the primary purpose and then adds relevant behavior details, making every sentence earn its place.

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 simple one-parameter tool, the description covers the essential context: what it loads, the parameter's optionality, and the backup behavior. It does not explain the difference from the similarly scoped rekordbox_importXml sibling, which prevents a perfect score, but overall it is reasonably complete for a tool with no 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 input schema has one parameter, xmlPath, with zero schema description. The description compensates by explaining that omitting xmlPath uses a default path set via library_setDefaultPath, adding meaningful semantics beyond the schema. It does not specify the path format, but the core behavior is covered.

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 'Load a Rekordbox XML file into the library,' which is a specific verb+resource combination. However, it does not differentiate itself from the sibling tool rekordbox_importXml, which may serve a similar purpose.

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 gives useful context about the optional xmlPath and the default path behavior, implying when the tool can be used. But it does not explicitly state when to use this tool versus alternatives like rekordbox_importXml, nor does it provide any exclusions.

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