notation_render

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

With no annotations, the description fully carries the burden of behavioral disclosure. It explains that bar lines are inferred from time signature and notes crossing bar lines are split and tied automatically. It also describes the pitch and duration format expected.

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 paragraph that efficiently conveys purpose, output, input formats, behavior, and usage advice. It is front-loaded with the main action and each sentence adds value, though it could be slightly more concise.

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 the tool's complexity and the lack of an output schema, the description provides good coverage of input formats and behavior. However, it does not explain all parameters (e.g., title, composer, tempo) in detail, leaving minor gaps.

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 coverage is only 33%, but the description adds significant meaning: it explains scientific pitch notation ('C4', 'F#5'), duration codes (w, h, q, etc.), and the structure of notes (shortcut strings vs. objects). However, parameters like title, composer, and tempo are not elaborated beyond the schema.

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 tool's purpose: 'Render music notation from a JSON score.' It specifies the output formats (SVG, MusicXML, MIDI) and distinguishes itself from sibling tools like notation_validate by advising to validate first.

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 description explicitly tells users when to use notation_validate instead ('if you are unsure your input is well-formed — validate is cheaper than render'). It also explains that bar lines are inferred and notes are automatically split, providing clear usage context.

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