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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, but the description adds valuable context beyond them: 'Pure math: free, instant, no key needed,' supported timecode frame rates, and the exact shape of the returned tempo map and hit placements. This tells the agent about cost, speed, auth requirements, and output semantics that structured fields alone do not provide.

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 dense but front-loaded: the core action comes first, followed by output-usage guidance and timecode support. Every sentence contributes useful information, though the middle sentence is packed with several ideas at once.

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?

There is no output schema, but the description fully specifies what is returned: tempo_map [{beat, bpm}] and hits[] with beat, bar, and beat-in-bar placement. It also covers input flexibility, timecode handling, and downstream tool integration, leaving no material gap for an agent calling this tool.

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 eight parameters. The description still adds meaning by explaining how hits can be bare numbers, objects with time_s or timecode, per-hit 'land' overrides, and how the tempo map stays near bpm but inside bpm_range. This is more than schema repetition and helps an agent assemble correct inputs.

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 verb and resource ('turn HIT POINTS into a TEMPO MAP') and explicitly distinguishes the tool's role from siblings by naming the downstream consumers (doseedo_render_midi, doseedo_render_score, doseedo_session_from_stems). An agent can tell this is a scoring-to-picture tempo-mapping utility, not a generic renderer or beat-grid analyzer.

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 clearly establishes the use case ('Scoring to picture') and what inputs to supply, plus where the output goes next. It lacks explicit when-not-to-use guidance or direct comparison to alternatives like doseedo_beat_grid, but the context is strong enough for an agent to select it correctly.

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