piano_roll_bridge

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

The description adds one meaningful behavioral trait beyond the annotations: the setup is 'one-time-per-process', which aligns with the non-idempotent annotation. However, it does not disclose what side effects occur (e.g., writing a bootstrap script) or what the 'arm' actually does at runtime. Annotations already indicate a mutating operation (readOnlyHint=false), so the description partially complements them but remains thin.

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 sentence with no filler, and the 'one-time-per-process' qualifier is front-loaded. It is appropriately short for a tool whose parameter semantics live in the schema, though the cryptic wording ('arm') sacrifices some clarity for brevity.

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?

Even with a rich schema and output schema present, the description leaves major context gaps: it never explains what the bridge is, why a separate runtime exists, what 'arm' means, or when the tool must be invoked relative to other piano roll tools. An agent cannot determine the prerequisite ordering or the tool's role in a workflow from this description alone.

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%: both parameters have clear inline explanations, including the conditional need for confirm_user_ran_script. The tool description adds no parameter-level details, so the baseline of 3 applies because the schema carries the full semantic weight.

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 identifies a specific resource (the one-time-per-process arm for FL's separate Piano Roll script runtime) but uses the vague verb 'manage' without naming the actual operations (status, prepare, confirm). It distinguishes itself from sibling note-reading/writing tools by focusing on the runtime bridge, but an agent would still need to open the schema to understand what the tool actually does.

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 given about when to use this tool or how it relates to alternatives like piano_roll_read_notes or piano_roll_write_notes. The 'one-time-per-process' phrase implies a setup scenario, but it never states whether this should be run before other piano roll tools or what the intended workflow is.

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