get_session_context

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

With no annotations provided, the description carries the full burden. It clearly implies a read-only operation ('Returns a snapshot') and details the contents, plus the behavioral recommendation to call once due to assumed session state stability. It does not disclose potential size or performance implications, but these are minor for a snapshot tool.

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?

Two sentences: the first is front-loaded with the primary purpose and a concise list of contents, the second gives crisp usage guidance. Every word earns its place with no fluff or repetition.

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 provides a solid overview of what is returned and when to use it, which is sufficient for a no-parameter, no-output-schema tool. It could be even richer by describing the output format or limitations, but it is complete enough for confident invocation.

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 schema coverage is trivially 100%. The baseline for 0 params is 4, and the description adds no unnecessary parameter details. It appropriately focuses on behavior and contents instead.

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 tool 'Returns a snapshot of the current Ableton session' and enumerates the specific contents (tracks, volumes, panning, mutes, sends, device chains, return tracks, master track, routing). This specific verb+resource combination distinguishes it from siblings like get_track_details, which focuses on a single track, or get_spectral_snapshot, which covers spectral data.

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?

Explicitly states when to use ('Call once at the start of a conversation to orient yourself') and when not to ('No need to call again unless the user says the session has changed'). It does not explicitly name alternative tools, but the timing and frequency guidance is strong.

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