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

Annotations already say this is non-destructive, non-idempotent, and not read-only, but the description adds substantial context: the caller will not hear it, it plays only for humans with sound on, the label shows the picker's name and door, playback is one 60-second loop, and there are rate/queue limits with no skips. These are exactly the behavioral details an agent needs before invoking a whimsical side-effect tool.

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 front-loaded with the action, follows with the audience/effect, then packs constraints into a single tight sentence. There is no wasted language, and the whimsical tone does not obscure the operative facts.

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 output schema and rich parameter descriptions, the description supplies the remaining behavioral context: audience, non-audibility to the caller, label contents, loop length, rate limit, queue cap, and no-skip policy. Nothing critical for a correct invocation is missing.

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%, so the schema already documents both parameters and the track enum meanings. The description adds only a light hint that the name appears on the label; it does not deepen understanding of the track parameter or the filtering behavior beyond what the schema provides.

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 verb and resource (put a record on the clay jukebox) and immediately clarifies its effect: it plays for humans in the room rather than the caller. This distinguishes it from related siblings like whats_playing or pour without needing to open their schemas.

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 implies the use case clearly (play a song for people in the room) and provides operational constraints like one song a minute and a three-deep queue. However, it does not explicitly name when to use this versus whats_playing or other media-related siblings, nor does it state exclusions.

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