navigate_view

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

No annotations are provided, so the description carries the full disclosure burden. It usefully explains non-obvious direction semantics ('zoom left' = zoom out in time, 'scroll left' = toward bar 1) and gives a rough scale (~3 steps fit a 64-bar song). It leaves the modifier parameter, other views, and any side effects or reversibility unaddressed.

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?

Two tight sentences, front-loaded with the core action and followed by the clarifying example. No padding, though the wording is slightly convoluted.

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 5 parameters at 0% schema coverage, no annotations, and no output schema, the description only explains one parameter's semantics in one view. An agent would have to guess the effect of 'modifier', the meaning of 'steps' numerically, and behavior in views other than the Arranger.

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% across 5 parameters, so the description must compensate and largely does not. It clarifies 'direction' for zoom/scroll in the Arranger and hints at 'steps' magnitude, but 'view', 'modifier', and the action enum's behavior remain undefined in both schema and description.

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 verb pair (zoom/scroll) and resource (view), and the arrow-key analogy makes the intent immediately clear. It is distinguishable from siblings like show_view, though the description never names an alternative explicitly.

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?

The arrow-key analogy implies when this is used (navigating the Arranger viewport), and the Arranger example gives concrete context. However, there is no guidance on when to prefer this over show_view, nor on how action/direction/modifier should be combined.

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