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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context — the tools are browser-based on cajon.pro and require no sign-up — but says nothing about what is actually returned (a list of tool names, links, or descriptions) or whether it is static content.

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 sentence with the resource and site front-loaded, followed by a compact enumeration of tools and rhythm styles. Every clause carries information, though the list of rhythm genres is slightly longer than strictly needed.

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-parameter listing tool with no output schema, the description conveys both the source (cajon.pro) and the full catalog of what the agent will find, which is the important missing piece when no output schema exists. The only gap is not stating the return shape explicitly.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing parameter behavior.

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 names the resource precisely and enumerates its contents (virtual cajon, metronome, drum machine, tap-tempo BPM finder, song drum parts, rhythm library), so an agent knows what it surfaces. It lacks an explicit verb describing the operation (e.g., 'returns a list of'), but the scope is unambiguous.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the siblings cajon_catalog, find_drum_schools, or find_songs, even though 'song drum parts' partially overlaps with find_songs. Usage is only inferable from the phrase 'for drummers and cajon players' and 'No sign-up'.

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