save_brand_kit

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose that the tool saves a named configuration with BPM, vocal, and mood constraints, but it does not say whether saving an existing name overwrites the kit, whether the operation is idempotent, what permissions are required, or what side effects occur. For a mutation tool with zero annotation coverage, this is a notable 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?

Two sentences with no filler. The core action and constraints are front-loaded, and the cross-reference to recommend_bgm is directly useful for an agent deciding how to chain calls.

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?

The description establishes the brand kit concept and its relation to recommend_bgm, which covers the main workflow context. However, with 8 parameters, no annotations, and 0% schema description coverage, the description leaves important operational details (overwrite behavior, optional-field semantics, allowed values) unspecified. An output schema exists, so return values need not be explained, but the overall guidance is only minimally adequate.

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 0%, so the description must compensate. It maps 'BPM lock' to bpm_min/bpm_max, 'no vocals' to instrumental_only, and 'mood whitelist' to moods. But name, avoid, genres, and notes are left undocumented beyond their parameter titles, and the description gives no accepted values or format hints for array/string 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?

The description states a specific action ('Save') and resource ('brand kit'), and the parenthetical clarifies what the brand kit encodes: BPM lock, no vocals, and mood whitelist. It also names the intended downstream consumer, recommend_bgm. It does not explicitly contrast itself with sibling tools such as search_music or generate_bed, so it stops short of a 5.

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 instruction 'Pass brand_kit=name to recommend_bgm' gives a clear workflow hint: save the kit first, then reference it by name during recommendation. However, it never explicitly says when to use this tool versus alternatives like recommend_bgm or search_music, so the usage guidance is implied rather than stated.

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