get_scale_notes

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

No annotations are present, so the description must fully disclose behavior. It states the tool retrieves scale notes but does not specify the return format (e.g., MIDI note numbers vs note names), possible ranges, or whether it operates on the session scale or an arbitrary one. This lack of detail is a significant gap for a read operation.

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 succinct and front-loaded, immediately stating the purpose followed by a clear parameter list. Every sentence has value, and the format is easy to scan with no redundant text.

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 tool's simplicity (2 parameters, no output schema), the description covers purpose and parameters adequately. However, it omits the return value format, which is critical since no output schema exists. This prevents the agent from predicting the tool's output structure, so the description is not fully complete.

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 description provides detailed parameter semantics beyond the schema: it explains root as 'MIDI note number for the root (0-127, where 60 = middle C)' and lists all valid scale_type values. This fully compensates for the schema's 0% description coverage, adding essential meaning not present in the structured data.

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 clearly states the function: 'Get the notes in a musical scale.' This is a specific verb+resource that distinguishes it from siblings like get_song_scale_names (which returns scale names) and set_song_scale (which sets the scale).

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?

No guidance is provided about when to use this tool versus alternatives, nor any prerequisites or exclusions. The description simply states what it does without contextualizing when it would be the appropriate choice, leaving the agent to infer usage.

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