project

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

There are no annotations, so the description must carry the behavioral disclosure burden. Saying 'edits' signals mutation but does not explain side effects, destructiveness, dependencies between actions, or what happens to existing project state.

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 text is tightly written, front-loaded, and contains no wasted words. However, it is under-specified for a tool with ten parameters and four action modes, so its brevity reflects incompleteness rather than well-judged scoping.

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 annotations, no output schema, and 0% parameter coverage, the description needs to supply substantial context but only provides a phrase and an action list. It gives minimal orientation but is not sufficient to invoke the tool correctly across its different actions.

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 0%, and the description adds no parameter semantics beyond repeating the action enum that already exists in the input schema. It does not map bpm, numerator/denominator, start/end_beats, or position_beats to the relevant actions, so an agent cannot determine which parameters apply to which action.

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 the resource (project) and the operation class (edits), then enumerates the four edit actions: tempo, time_signature, time_selection, and marker. This gives an agent a concrete sense of what the tool does, though it does not explicitly contrast it with sibling tools.

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?

No guidance is provided for when to use this tool versus siblings such as track, item, reaper_call, or run_lua. The action list implies project-level usage, but the description does not specify conditions, exclusions, or alternatives.

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