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

With no annotations provided, the description fully discloses the tool's behavior: it reads existing notes, computes target onsets, distributes notes round-robin or to nearest onset, and optionally adjusts velocity/duration. Edge cases like pattern cycling and note distribution are explained, making the tool's behavior completely transparent.

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 well-structured with a clear introductory sentence, a 'How it works' section, parameter definitions, and an example. Every sentence contributes meaning, and there is no redundancy. It is comprehensive yet 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 complexity of 8 parameters, no schema descriptions, no annotations, and an output schema, the description covers all necessary context: algorithm steps, parameter details, edge cases, and return value. It is fully sufficient for an agent to select and invoke the tool 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?

The input schema has 0% description coverage, so the description must compensate. It does so thoroughly by explaining each of the 8 parameters, including their format, default values, and behavioral implications (e.g., velocity_mode options, rhythm_string vs onset_grid priority). This adds immense value beyond the raw 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: apply a rhythmic pattern to existing notes by repositioning onsets. It uses specific verb+resource ('apply a rhythmic pattern') and distinguishes itself as the inverse of 'extract_rhythm.' The sibling context is implicitly handled by explaining the relationship to extraction.

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 context for when to use the tool, including an example workflow with extract_rhythm. However, it does not explicitly state when not to use it or list alternative tools beyond mentioning its inverse relationship. The guidance is strong but lacks explicit exclusions.

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