list_options

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

No annotations are provided, so the description carries the full burden, yet it discloses no behavior: no indication that it is a read-only enumeration, what the return format is, or whether results are static. It only lists categories of options.

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?

A single compact sentence with no filler, front-loading the four option categories. It is efficient, though as a noun phrase fragment it lacks a clear subject/verb structure.

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?

With no output schema and no annotations, the description should at least sketch the return shape (e.g., a mapping of category to accepted values). It enumerates the categories it will return, which is adequate for the caller to know what to expect, but leaves the structure unspecified.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline is 4. The description's mention of accepted categories is the only semantic content needed for a parameterless lookup.

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 names the option categories (instruments, accompaniment styles, lyric modes, chord qualities) but never states a verb or that it returns the accepted values. An agent can infer enumeration from the name 'list_options', but the fragment alone doesn't distinguish it as a lookup versus a mutation.

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?

No when-to-use guidance is given. It doesn't say to call this before create_song to discover valid option values, nor mention any alternative or prerequisite, leaving the agent to guess its role relative to create_song and render_backing.

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