Descubrir medios de una canción

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

Annotations already declare readOnlyHint=true, and the description adds that it works 'sin abrir REAPER', indicating a non-invasive discovery process. It also clarifies the scope of results (stems, MIDI, reference, suggested pairs) but doesn't disclose error handling or return value details.

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?

One concise sentence in Spanish that front-loads the core action and scope. No redundant words; every element earns its place.

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 simple read-only discovery tool with an output schema, the description covers the key function and the 'no REAPER' benefit. It could elaborate on what 'pares sugeridos' means or how results should be used, but it's adequate for the tool's complexity.

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 0%, and the description does not elaborate on the song_name parameter. The schema only provides type and length constraints, leaving meaning to be inferred from the parameter name. This is a gap for a tool with only one parameter.

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 the specific verb 'Encuentra' (finds) and enumerates concrete resources: stems, MIDI, reference and suggested pairs. This clearly differentiates it from sibling tools like analyze_midi or import_audio, which have different purposes.

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 'sin abrir REAPER' implies it is a lightweight lookup that doesn't require launching the DAW, giving some usage context. However, it doesn't explicitly state when to prefer this over alternatives like analyze_midi, nor does it mention exclusions or prerequisites.

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