piano_roll_clear

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

Without annotations, the description must disclose behavioral traits. It states 'Remove every note' implying destruction, but lacks details on undo behavior, required permissions, or side effects. The minimal information does not fully inform the agent.

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 extremely concise—one sentence—but front-loads the action. It is appropriately short, yet could benefit from structure like bullet points or parameter hints. Conciseness is good, but not optimal for usability.

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?

Given two optional parameters and no annotations or output schema, the description is incomplete. It does not specify which piano roll is affected (channel/pattern), default behavior, or return values. An agent lacks sufficient context for correct invocation.

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 only mentions 'channel' implicitly. The 'pattern' parameter is not explained. The description adds little beyond the schema field titles, failing to clarify parameter meaning or usage.

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 verb 'Remove' and resource 'every note in the (channel's) piano roll.' It effectively conveys the core action of clearing all notes. However, it does not explicitly differentiate from sibling tools like 'piano_roll_delete_notes,' but the function is distinct enough for an agent to infer.

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 on when to use this tool versus alternatives. There is no mention of prerequisites, typical use cases, or situations where this tool should be avoided, leaving the agent without direction.

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