Export setlist to vault

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

The description adds useful behavioral context beyond annotations: it explains the output format (tracks array frontmatter), that it matches import_setlist's expectation, and that it is not destructive. No contradiction with annotations.

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 three sentences, front-loaded with the main purpose, and concise without redundancy. Every sentence adds value.

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 complexity (4 params, no output schema), the description covers the core functionality, output format, relation to import_setlist, and prerequisites. It lacks details on error handling or performance, but is sufficient for the task.

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?

All parameters are described in the schema with 100% coverage. The description adds further meaning, e.g., 'target' is a COMP with 'manage_cue snapshots', 'note' is the setlist note name, 'folder' matches import_setlist's location, and 'include_tempo' captures global tempo.

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 specifies the action (serialize/export), the source (COMP cue snapshots), the destination (vault note), and the purpose (round-trip shows). It distinguishes from siblings like import_setlist by mentioning the round-trip workflow.

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 states when to use (to export a live-built show into the vault for round-tripping) and mentions prerequisites (TDMCP_VAULT_PATH). It references import_setlist for re-import. However, it does not explicitly state when not to use or list alternatives.

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