mcp_opendaw_ppqn_to_seconds

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

With no annotations, the description must carry the burden. It does so by revealing that conversion integrates over tempo change events and defining the PPQN unit (960 pulses per beat). It also notes the return type and potential error. It could mention edge cases or lack of side effects, but the key behavioral nuance is present.

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?

Three short, focused paragraphs: the action, the tempo-automation context, and the parameter/return specification. No fluff, and each sentence adds value. The example and unit definition are compact.

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?

For a simple one-parameter conversion tool with an output schema, the description explains the conversion logic, the tempo-map behavior, parameter semantics, and return type. It could explicitly mention the inverse tool or edge cases (e.g., negative positions), but the available information is sufficient for an agent to invoke it correctly in most scenarios.

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 schema provides merely 'position_beats' as a number. The description adds that it is a float in beats, gives an example (4.0 = beat 4), and clarifies its semantic position. With 0% schema coverage, this fully compensates and exceeds the baseline.

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 opening sentence 'Convert a position in beats (PPQN units) to seconds using the project's tempo map' uses a specific verb and resource, clearly distinguishing it from the sibling inverse tool `mcp_opendaw_seconds_to_beats`. The scope is defined precisely.

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 explains that the conversion accounts for tempo automation and integrates over tempo changes, giving clear context for when this tool is necessary (accurate conversion in a non-constant tempo timeline). However, it does not explicitly name alternatives or state when not to use it, so it falls short of full usage guidance.

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