align_measurements

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

No annotations provided, so description carries the burden. It discloses that the result remains in the alignment tool's preview state and does not persist, and that the tool reports the computed delay. This is key behavioral context, though more detail on side effects could be useful.

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 concise, information-dense sentences. Front-loaded with the action, then role clarification, then next steps. Every sentence earns its 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?

With no output schema, the description indicates the primary output (the delay). It covers workflow and preview state. It does not detail output formatting or edge cases, but overall it is sufficiently complete for a tool with good schema coverage.

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 100%, so baseline is 3. The description adds role semantics (A as reference, B as delayed) and contextualizes frequencyHz as the crossover, enriching the schema definitions.

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 tool phase-aligns measurement B to A at a specified frequency and reports the computed delay. It distinguishes from siblings by specifying the phase-alignment use case and the preview-state result.

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?

Provides clear context: A is reference (mains), B is delayed (sub), frequency typically the crossover. Includes follow-up guidance (create_aligned_sum or apply delay in DSP), though it does not explicitly contrast with siblings like align_spl.

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