generate_and_place_bassline

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

With no annotations, the description bears full responsibility for behavioral disclosure. It conveys the basic generation and placement action, and partially explains complexity, but omits critical behaviors: whether it overwrites existing notes (despite the 'replace_existing' parameter defaulting to true), whether it creates a new clip or requires an existing one, and the side effects of placement. The description is inadequate for safe autonomous use.

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 extremely concise, using two sentences to convey the primary purpose and a key parameter nuance. Every element earns its place; there is no redundancy or fluff. The front-loaded structure quickly informs the agent of the core function.

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 (10 parameters, no schema descriptions, no annotations), the description is substantially incomplete. It fails to explain many parameters (e.g., style, key, scale, octave, seed), does not specify whether the tool creates a clip or modifies an existing one, and does not reference the output schema. The description leaves significant gaps that an agent would need to fill through inference or trial.

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 only adds meaning for one parameter ('complexity' range). The other nine parameters (track_index, slot_index, style, key, scale, octave, length_bars, replace_existing, seed) receive no semantic explanation, leaving the agent to infer from names alone. This is insufficient for a 10-parameter tool.

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 action ('Generate a bassline') and the target ('place it into a MIDI clip'), providing a specific verb and resource. However, it does not explicitly differentiate from sibling generation tools beyond the tool's name itself, so it's clear but not maximally distinctive.

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 provides minimal usage guidance, only explaining the 'complexity' parameter's meaning. It does not state when to use this tool versus alternatives (e.g., generate_and_place_melody), nor does it offer any exclusions or prerequisites. This leaves the agent with little context for decision-making.

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