cassette_match_bgm

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

With no annotations, the description must carry the behavioral disclosure burden. It reveals that registration is optional, but does not explain side effects, whether the session is modified, what 'register' means, or any prerequisites or failure behaviors. The schema hints at fallback and optimization flows, which the description ignores.

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 a single, front-loaded sentence with no filler or redundancy. Every phrase adds meaning and it is easy to parse quickly, even if more content is needed elsewhere.

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 tool with seven parameters, no annotations, and no schema descriptions, this one-line description is far too sparse. The tool's fallback, continuation, and optimization behaviors are completely unexplained, and the relationship to sibling matchers 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 0%, yet the description offers no explanation of the seven parameters, including required ones like instruction and search_queries. The agent gets no help understanding how these values shape the matching or registration 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 uses a specific verb ('Match') and resource ('Free To Use background-music asset'), and adds the 'optionally register' nuance. It reads as a clear purpose, though it does not explicitly contrast with the similarly named sibling cassette_match_exact_bgm.

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?

It states what the tool does but gives no guidance on when to use it versus alternatives like cassette_match_exact_bgm or jamendo_music_matcher. There is no mention of when-not scenarios, fallback conditions, or when registration should be enabled.

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