health_check

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'check if connected and responsive' without specifying what happens on failure (e.g., error, boolean return) or any side effects. This is minimal transparency.

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 extremely concise with two short sentences. Every word is necessary, and there is no redundant or filler content. It is well-structured for immediate understanding.

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?

The description is adequate for a simple no-parameter tool, but it lacks specifics about the return value (e.g., boolean or error message) and what 'responsive' entails. Given its simplicity, it is moderately complete but could be improved with a brief note on output.

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, and the description covers that fully. With no params, a baseline of 4 is appropriate, and the description adds no additional parameter meaning beyond what is already clear.

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 it checks connectivity and responsiveness of Ableton Live. It uses a specific verb ('check') and resource ('Ableton Live'), and it is distinct from sibling tools like get_cpu_load or session info tools.

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 that the tool should be used to verify Live's connection and responsiveness before other operations, but it does not explicitly state when to use or avoid this tool compared to alternatives like get_cpu_load or is_session_modified.

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