Beatwise Metronome

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

The description goes beyond the read-only annotations by explaining that it accepts BPM or a note duration and returns whole-to-sixty-fourth values, dotted and triplet variants, pre-delay suggestions, and approximate Italian marking ranges. It also clarifies domain constraints such as BPM 20 to 400, up to 100000 bars, and that hertz here means rhythmic repetition rather than pitch.

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 appropriately front-loaded with 'Use this when' and remains compact enough for the number of use cases covered. The keyword-list opening is somewhat dense, but every sentence contributes scope, constraints, or a clarifying boundary.

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 seven optional parameters, full schema description coverage, read-only annotations, and an output schema, the description supplies enough context to select and invoke the tool correctly. It covers supported inputs, major constraints, output categories, and non-audio boundaries without needing to restate the full schema.

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 the baseline is 3, but the description adds useful semantics by clarifying the BPM-or-note-duration input mode and the meaning of hertz in this context. Most BPM and bar-limit details are repeated from the schema, which keeps it from a 5.

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 what the tool calculates: BPM-to-ms conversions, note-cycle hertz, milliseconds-to-BPM, bar length, and song length. It is specific about the resource and outputs, but it does not explicitly distinguish this tool from sibling tools like show_metronome or plan_tempo_practice.

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?

It gives clear triggering scenarios such as 'bpm to ms', 'delay time calculator', and 'bar length or song length', plus a useful exclusion that it does not record audio or detect pitch. It stops short of naming alternatives or explicitly saying when a sibling tool should be used instead.

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

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

Annotations already cover read-only, non-destructive, closed-world behavior. The description adds substantial operational detail: returned artifacts, ascending/descending support, 20-400 BPM range, up to 200 stages, percent-step rounding, target-stage timing, and explicit non-capabilities.

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 compact and front-loaded with the usage trigger. Each sentence carries useful information: the use case, the outputs, the operational limits, and the exclusions.

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 an output schema present, the description need not detail return fields, and it already summarizes key outputs. Given the annotations and full schema coverage, it provides enough context for an agent to select and invoke the tool correctly.

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 100%, so the schema already documents all five parameters. The description adds a few useful hints, such as ascending/descending and the 200-stage cap, but it does not meaningfully enrich the per-parameter semantics beyond what the schema provides.

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 states a specific use case: building a tempo ladder from start to target BPM with step and minutes per stage, and returning a ladder table, total time, and CSV. It is clear what the tool does, but it does not explicitly name or contrast with the sibling tools calculate_tempo_values or show_metronome.

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?

It gives a clear trigger: 'Use this when the user wants a metronome for practice with a tempo ladder...'. It also notes what the tool does not do (track sessions or record audio), but it does not explicitly say when to prefer a sibling tool such as show_metronome or calculate_tempo_values.

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

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

Adds substantial behavioral context beyond the annotations: the widget runs only while on screen, audio timing depends on the device, and the tool does not record audio or detect pitch. These details help an agent understand practical limitations and non-capabilities.

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 dense paragraph with the usage trigger front-loaded, and most sentences carry useful information. Some keyword repetition and feature listing make it slightly less tight than ideal.

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 annotations, full schema coverage, nested ramp object, and existing output schema, the description is complete enough for an agent to call the tool correctly. It covers the live-widget behavior, limits, timing caveats, and what the tool does not do.

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 100%, so parameter details are already fully documented. The description reinforces major ranges and features such as 20–400 BPM, 1–16 beats, accents, subdivisions, and ramps, but does not add much parameter-specific meaning beyond the schema.

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?

States a specific action and resource: it opens a live metronome beat widget with detailed capabilities. The purpose is very clear, but it does not explicitly distinguish itself from sibling tools like calculate_tempo_values or plan_tempo_practice.

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?

Begins with a clear trigger: 'Use this when the user wants a metronome...' and lists relevant user intents such as tap tempo or practice. It gives strong positive guidance but does not state when to prefer the sibling calculation or planning tools instead.

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