get_song_musical_context

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

The readOnlyHint and destructiveHint annotations already establish that this tool is safe and read-only, so the description's main contribution is clarifying the exact domain scope. It adds the list of musical attributes but does not disclose further behavioral details such as return structure or behavior when context is absent.

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 sentence with the verb front-loaded and a compact list of resources. Every word contributes meaning, and there is no redundancy or filler.

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 read-only getter, the description is largely complete: it names the categories of information returned and the annotations cover the safety profile. The only minor gap is the slightly vague phrase 'Arrangement loop context,' which is not further defined.

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 has zero parameters, so the baseline is 4 and the description does not need to compensate for parameter documentation. It adds clarity by naming what data the tool returns, which is more than the empty 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?

The description clearly states a read operation and enumerates the specific resources: key, scale, time signature, quantization, groove, swing, and Arrangement loop context. This distinguishes it from the paired set_song_musical_context tool, though it does not explicitly differentiate it from related getters like get_clip_groove_context.

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 usage through the verb 'Read' but provides no explicit guidance on when to choose this tool over alternatives. It does not mention the setter counterpart, clip-level context tools, or any exclusions.

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