notation_validate

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

Without annotations, the description carries the burden of disclosing behavior. It mentions it returns errors with fix suggestions and is cheaper, but does not explicitly state that the tool is read-only, idempotent, or free of side effects—common expectations for a validation tool but not confirmed. More explicit behavioral context would be beneficial.

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 two concise sentences. The first sentence states purpose and output; the second gives usage guidance. No repetition or filler. Essential information is front-loaded.

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 absence of annotations and output schema, the description covers purpose and usage but omits detail on error types, fix suggestion format, input limitations, or edge cases. It provides a minimal but functional level of completeness, with room for more context.

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?

The input schema has 6 parameters with 0% description coverage; the description adds no parameter-specific meaning. While parameter names (title, composer, tempo, etc.) are self-explanatory, the description fails to clarify constraints, relationships, or how parameters influence validation. This is a significant gap.

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 explicitly states the tool validates an input shape without rendering, distinguishing it from the sibling notation_render. It uses specific verbs ('validate') and identifies the resource ('input shape'), making the purpose unmistakable.

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 provides clear guidance: 'Cheaper than notation_render — use this when iterating on input shape.' It tells the agent when to use (during iteration) and implies an alternative (notation_render for actual rendering).

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