create_group

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

With no annotations, the description carries the burden of behavioral disclosure. It explains that the group is empty, returns the group index, and inherits SV's default singer, adding useful behavioral context. However, it does not mention error handling (e.g., invalid track) or side effects beyond creation, which keeps it from a 5.

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 two sentences, front-loaded with the main action, and efficiently provides context about the SV singer assignment and sibling tool behavior. No wasted words.

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 only two parameters and no output schema, the description covers the essential aspects: what it does, when to use it, and what it returns (group index). It also explains the singer inheritance, making it sufficiently complete for this tool's complexity.

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 the baseline is 3. The description adds little beyond the schema, though it does clarify the track is the target and mentions the optional name is for the new group. This is consistent with the schema's own descriptions.

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 'Create a new empty note group on a track and return its group index,' which specifies a clear verb and resource. It also distinguishes itself from the sibling insert_notes by noting that insert_notes can auto-create a group when the track has none, making this tool's purpose more specific.

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 when to use this tool ('the usual first step before insert_notes when no suitable group exists yet') and mentions an alternative behavior ('insert_notes also auto-creates a group when the track has none'), providing clear contextual guidance.

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