get_rhythm

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the safety burden is off the description. The description usefully discloses the output encoding (x = hit, . = rest) and that patterns come in named/Euclidean/polyrhythmic flavors. It doesn't say whether 'name="list"' enumerates options or anything about determinism, but against the annotation this is adequate.

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?

A single clean sentence that front-loads the output format before the categories. Efficient and mostly waste-free, though the parenthetical notation and 'named timelines (clave, tresillo, bell patterns)' could be tightened.

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?

For a zero-required-parameter, read-only lookup with no output schema, the description covers the essential missing piece – the shape of the returned step string – and the three modes of generation. An agent has enough to call it, though it could note what 'name=list' returns.

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 high (~80%), so the schema already documents name, polyrhythm, euclid_hits, and euclid_steps. The description still adds conceptual mapping – grouping parameters into 'named timelines', 'Euclidean rhythms' and 'polyrhythms' – which helps an agent pick the right parameter family. It doesn't add format/syntax 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?

States a specific resource (rhythm patterns) and the exact output format ('step strings', 'x = hit, . = rest'), plus the three generation modes. It also names the downstream consumer add_drum_pattern, which situates it in the workflow. However it doesn't explicitly distinguish itself from adjacent generative tools like add_genre_groove or write_bassline beyond the drum-pattern linkage.

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 phrase 'ready for add_drum_pattern' implies the intended follow-on step, giving implied usage. But it never says when to choose this over alternatives (e.g. add_genre_groove) or that no arguments are required to list patterns. Usage is inferable, not stated.

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