get_session

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

No annotations are provided, so the description must fully convey behavioral traits. It only says 'Get' which implies a read-only operation, but it does not clarify prerequisites (e.g., a session must be open), side effects, or permissions. The description lacks sufficient transparency beyond the obvious read nature.

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: one sentence of 10 words that immediately conveys the tool's purpose. It front-loads the key action and output, wasting no words.

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?

Given the tool has no parameters and an output schema exists (not shown), the description adequately covers the key information needed. It lists the main attributes returned. However, it could slightly benefit from noting that it returns the full current session state, but it is mostly complete for a read-only parameterless tool.

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 documentation coverage is effectively 100%. The baseline for 0 parameters is 4, and the description does not need to compensate for param info. It adds no parameter-specific details, which is acceptable.

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 reads the current Ableton session state and lists specific attributes (tempo, time signature, playback status, loop settings). It uses a specific verb ('Get') and resource ('current Ableton session state'), distinguishing it from siblings like get_song_info or get_track.

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 this tool should be used when you need global session parameters, but it does not explicitly state when to use it over alternatives like get_song_info or get_track. No when-not-to-use guidance or exclusion criteria are provided.

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