generate_polyrhythm

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

No annotations are provided, so the description must fully disclose behavioral traits. It offers no information on what the tool does beyond the name—no indication of output format, side effects, performance characteristics, or error conditions. This is inadequate for a tool with parameters and no output schema.

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—two words—with zero wasted text. It is front-loaded and efficiently communicates the core function, though this comes at the cost of detail. Every word earns its place, making it structurally optimal for brevity.

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 has 2 parameters, no annotations, and no output schema, the description is incomplete. It fails to explain what a polyrhythm is in this context, what the output entails, or how parameters interact. For a generative tool in a music/pattern domain with many siblings, this leaves critical gaps for an agent.

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 100%, with both parameters ('sounds' and 'patterns') documented in the schema. The description adds no meaning beyond this, not explaining what constitutes valid sounds or patterns (e.g., file paths, instrument names, rhythm ratios). Baseline 3 is appropriate as the schema handles the documentation burden.

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 'Generate polyrhythm' is a tautology that merely restates the tool name without elaboration. It lacks specificity about what resource or output is generated (e.g., audio, notation, pattern data) and how it differs from sibling tools like 'generate_pattern' or 'generate_euclidean'. This provides minimal guidance to an agent.

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. With many sibling tools for pattern generation (e.g., generate_pattern, generate_euclidean, generate_drums), the description fails to indicate context, prerequisites, or exclusions. This leaves the agent with no basis for selection.

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