Export setlist to vault

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

The description adds valuable context beyond the annotations: it reveals the note frontmatter structure, the COMP snapshot key, the prerequisite TDMCP_VAULT_PATH, and the round-trip workflow with import_setlist. It does not disclose behavior if the note already exists or if the COMP has no cues, but given the annotations, this is a minor gap.

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 four sentences, information-dense, and front-loaded with the primary action. It uses some jargon (COMP, tdmcp_cues) but each sentence contributes essential context, and it is not overly verbose.

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 100% schema coverage, annotations, and no output schema, the description is complete: it explains the note format, prerequisites, and the re-import path. It fully covers the intended use case and relationships to sibling tools.

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 description coverage is 100%, so parameters are already well-defined. The description enhances the target parameter by specifying the 'tdmcp_cues' key and explains the relationship with import_setlist, adding meaning beyond the schema for the target and include_tempo parameters.

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?

Purpose is crystal clear: it serializes cues from a COMP into a setlist note in Obsidian, with specific format details and a round-trip purpose. It cites the 'tdmcp_cues' key and names import_setlist as the counterpart, distinguishing it from other export tools.

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 explicitly states the use case: round-tripping a live-built show into the vault as a git-diffable setlist, and it names import_setlist for re-import. However, it does not explicitly contrast with alternative export tools (e.g., export_network_to_vault) or state when not to use it.

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