add_clef

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

No annotations are supplied, so the description carries the full behavioral burden and delivers almost nothing beyond clef value names. It does not say what is mutated, whether existing events shift, how bar/beat/pos interact, whether voice must already exist, or what the tool returns.

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 a single truncated fragment ending in an ellipsis rather than a complete sentence, so it is under-specified rather than concise. The most informative part (the valid clef values) is the very part that is left unfinished.

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?

A 6-parameter mutation tool with no annotations, no output schema, and 0% schema coverage needs a full explanation of placement semantics and preconditions. This definition provides essentially none of that, leaving the agent unable to call it correctly.

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 6 parameters, so the description must compensate and mostly does not: only the clef string is partially enumerated (and the list is cut off with an ellipsis). Bar, pos, beat, flow, and voice — including which are required — receive no explanation at all.

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 fragment "A clef change on the voice's staff" identifies the resource and effect, but omits an explicit verb and reads as a truncated note rather than a statement of purpose. The trailing list of clef values is useful but is not a purpose statement, and nothing distinguishes this from siblings like add_voice or add_interval.

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 when-to-use guidance, no prerequisites, no mention of alternatives, and no exclusions. An agent cannot tell from this text when a clef change is the right action versus other add_* operations.

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