marker_add

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

No annotations are provided, so the description bears full weight. It implies an additive action ('drop a marker') but does not state side effects like overwriting existing markers, undo behavior, or whether markers appear in a specific arrangement track.

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 a single concise sentence with no redundant words or extra details. It front-loads the action and object.

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 tool is simple and low-risk, but the description does not explain what a marker is in the context of the DAW, whether start_beats is absolute or relative, or what happens after the marker is dropped. No output schema is provided, so return behavior is also 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 description's phrase 'at a beat position' partially clarifies start_beats, but 'name' and 'length_beats' are not mentioned at all. Schema defaults are not explained, leaving the meaning of length_beats ambiguous.

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 verb 'Drop a marker' and the resource 'marker' along with the position 'at a beat position.' It distinguishes the tool's function from other composition/edit tools.

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 mention of when to use this tool versus alternatives such as clip_add or midi_clip_add. The description does not provide any conditional guidance or contrast with sibling tools.

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