get_session_info

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

With no annotations and no output schema, the description carries the full behavioral burden, and it does the most important part well by enumerating the return payload (tracks with devices and clips by slot, return tracks, master, scenes, selection). 'Snapshot' clearly implies a read-only operation, though it says nothing about payload size or performance for large sets.

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 tightly-packed sentence that front-loads the resource ('Snapshot of the Live set') before the itemized contents. Every listed element is meaningful content rather than filler, though the dense enumeration is slightly hard to scan.

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 tool with no annotations or output schema, the description is nearly self-sufficient: it tells the agent exactly what comes back. The remaining gap is routing guidance against the numerous get_* siblings and any note about response size.

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 takes zero parameters, so the baseline of 4 applies. There is no parameter surface for the description to explain, and nothing is missing.

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?

States a specific verb+resource ('Snapshot of the Live set') and enumerates exactly what the snapshot contains (tempo, tracks, devices, clips, return tracks, master, scenes, selection). This distinguishes it implicitly from narrower siblings like get_track_info or get_arrangement_clips, but never names them explicitly, so differentiation is left to inference.

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?

Usage is only implied: a full-session snapshot is self-evidently the 'get everything' call. There is no explicit guidance on when to prefer this over the many narrower get_* siblings (get_track_info, get_device_parameters, get_routing), and no stated exclusions or prerequisites.

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