ass_karaoke_styles

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

With no annotations, the description carries the full burden and does well: it discloses the exact style values written, that create=False is non-destructive, and that the return separates 'created' from 'existing'/'created_now', implying existing styles are not clobbered. It omits any error/permission behavior and does not explicitly confirm create=True is a document mutation.

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?

Purpose is front-loaded, then the style spec, the prefix rule, the non-destructive read note, and the return shape. The long attribute enumeration (Arial 60, colors, outline, Encoding 1...) is verbose but genuinely informative for a template tool, so most sentences earn their place.

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?

No output schema and no annotations, yet the description supplies the return structure and the mutation/non-mutation distinction, which is what an agent needs. The unaddressed doc_id semantics and the lack of any sibling routing are the remaining gaps.

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 coverage is 0%, so the description must compensate. It does for two of three params: 'create=False' semantics and the 'prefix' renaming pattern ('prefix', 'prefix_2', 'prefix_3'), plus the defaults inherited from the schema. doc_id is never mentioned, leaving one parameter undocumented in both schema and description.

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 verb+resource ('List (and optionally create) the conventional karaoke template styles') and names the concrete artifacts (Karaoke/Karaoke_2/Karaoke_3, prefix variants). It does not distinguish itself from near-siblings such as ass_karaoke_template, ass_add_style, or ass_list_styles, so an agent must infer the boundary.

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?

'create=False reports what exists without touching the document' gives one clear conditional for the read path, but the description never says when to prefer this tool over the sibling style-creation/list tools, nor what preconditions (e.g. an open document) apply. Usage is implied rather than routed.

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