Build Song Manifest Artifacts

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

Description adds atomicity context ('record both artifacts atomically') beyond annotations (all false), but lacks details on side effects like file overwrites or manifest state changes. Annotations already indicate non-readonly and non-idempotent, so description provides modest additional value.

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 single sentence is highly concise (18 words) and front-loaded with the core action: 'Build a verified accompaniment WAV and native VSQX'. No extraneous information.

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's complexity (building two artifacts from a manifest revision) and the presence of an output schema, the description fails to mention prerequisites like manifest existence or verification steps. Sibling tools like 'vocaloid_preflight_song' suggest a workflow order that is not addressed.

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 60%, placing it in the middle range. The description reinforces the purpose of manifest_path and expected_revision via 'from one immutable manifest revision', but does not clarify response_format or expected_revision semantics beyond the schema's minimal coverage.

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 verb 'build' and specifies the resources: 'accompaniment WAV and native VSQX'. It distinguishes from sibling tools like 'vocaloid_create_song_manifest' by specifying 'from one immutable manifest revision', making it unique.

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 the tool is used when you have a specific manifest revision and need to generate artifacts, but it does not provide explicit when-to-use or when-not-to-use guidance, nor alternative tool references.

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