get_tempo_map

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

readOnlyHint=true already establishes this is a safe read. The description adds value by disclosing the shape of the returned data (change locations and ramp flags), which annotations cannot convey, but it says nothing about scope (whole project vs selection) or the format of the ramp/location values.

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?

One compact sentence that front-loads the main resource and then lists the two supplementary data points. Zero waste, though the relative-clause phrasing ('with where each happens and whether...') is slightly less scannable than a plain enumeration.

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 parameters and no output schema, the description carries the entire burden and does reasonably well by enumerating what comes back (tempo changes, time-signature changes, positions, ramp behavior). A note about project scope or value format would make it fully complete, but for a simple read tool this is close.

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 tool takes zero parameters, and the schema is empty, so there is nothing for the description to document. The baseline of 4 applies for a parameterless tool.

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 resource: the project's tempo and time-signature changes, plus where each occurs and whether it ramps. This is specific enough to distinguish it from get_rhythm or get_project_overview, though it uses a noun phrase without an explicit retrieval verb and never names the obvious counterpart set_tempo_map.

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?

There is no when-to-use guidance, no prerequisites, and no reference to alternatives such as set_tempo_map (the write counterpart) or set_tempo. The agent must infer that this is the read-side of the tempo-map pair purely from the name.

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