rekordbox_exportXml

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

With no annotations, the description must carry behavioral context, but it only says 'Creates automatic backup.' This is vague and does not clarify whether existing files are overwritten, if directories are created, or if the operation is safe/read-only. The tool writes to a file system, but side effects and permissions are undisclosed.

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 concise, with two short sentences. The first states the primary action, and the second adds a useful note about backup. No filler or redundant information is present.

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 simplicity (one parameter, no output schema, no annotations), the description is incomplete. It does not mention return values, error handling, whether the backup is automatic before overwriting, or how the output path should be structured. The sibling list includes similar tools, but the description lacks sufficient detail for an agent to safely invoke it without guesswork.

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?

Schema coverage is 0%, and the description does not explain the outputPath parameter. While the purpose implies outputPath is the destination for the XML file, it does not specify whether it is a full file path, a directory, or the expected format. The agent must infer meaning from the tool name and context.

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 exports the library to a Rekordbox XML file, providing a specific verb and resource. It does not explicitly distinguish from sibling tools like rekordbox_importXml or library_exportJSON, but the format and direction (export) are clear.

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 on when to use this tool versus alternatives, such as exportJSON or importXml. The description does not mention any prerequisites, exclusions, or recommended use cases beyond the basic action.

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