get_ableton_status

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds that it returns 'basic project info,' which is some behavioral context. It doesn't specify what happens on connection failure (error vs. degraded status), but with a read-only idempotent check tool, the annotation coverage is adequate and the description adds modest value.

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?

A single, complete sentence that conveys the tool's purpose with zero wasted words. Front-loaded with the primary action (check connection) and secondary detail (return project info). Appropriate for a zero-parameter diagnostic tool.

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, idempotent status tool with an output schema, the description is largely complete. It covers purpose and return content. It could arguably mention failure behavior (what happens if Ableton isn't connected), but given the tool's simplicity, annotations, and output schema, this is a minor gap.

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?

This tool has 0 parameters, so there's nothing for the description to explain beyond confirming it's a no-argument request. The description's mention of returning project info clarifies the output behavior. With no parameters, the description doesn't need to add parameter semantics, and it appropriately stays silent.

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 what it does: checks the connection to Ableton Live and returns basic project info. The verb 'check' with specific resource 'Ableton Live' is clear. However, it doesn't explicitly distinguish from siblings like analyze_audio or preview_mix, though given the tool name and single-purpose nature (status check), differentiation is reasonably implied.

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 it's a pre-flight/diagnostic tool for verifying Ableton connectivity, but doesn't explicitly state when to use it (e.g., before other Ableton-dependent operations) or when not to use it. Given sibling tools like analyze_audio and auto_mix likely depend on Ableton, some usage context would help but it's not critically misleading.

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