mcp_opendaw_ppqn_to_seconds

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains that the tool accounts for tempo automation and integrates over tempo change events, and notes the return type (float or error). However, it does not mention side effects, authorization needs, or edge cases, which is adequate for a simple read-only conversion tool.

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 concise (5 sentences) with a clear structure: purpose, behavior, unit definition, parameter explanation, and return value. Every sentence adds value without redundancy.

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 simple single-parameter conversion tool and the presence of an output schema (per context signals), the description covers all necessary aspects: operation, input, account for tempo map, and return type. No additional context is needed.

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 input schema provides only the parameter name and type; the description adds meaning by specifying the unit (beats), example value (4.0), and context (position in beats). This goes beyond the schema, which has 0% coverage.

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 specifies the tool's purpose: converting a position in beats (PPQN units) to seconds using the project's tempo map. It defines the unit (1 beat = 960 pulses) and distinguishes the tool from siblings like 'seconds_to_beats' and 'ppqn_to_parts'.

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 when to use this tool—when conversion accounts for tempo automation and integrates over tempo changes. It does not explicitly state when not to use it or list alternatives, but the context is clear enough for an agent to decide appropriately.

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