get_session_info

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

With no annotations, the description carries the transparency burden. The verb "Get" implies a read-only, non-destructive operation, but the description does not state what exactly is included in the session information, nor does it explicitly confirm no side effects.

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, front-loaded sentence contains exactly the necessary identifying information. No filler, repetition, or unnecessary structure.

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 that this is a no-argument getter with an output schema, the description is mostly complete: return values are presumably covered by the schema, and the action is clear. The main missing piece is usage context relative to sibling tools, but this is a simple enough tool that the description remains sufficient.

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 schema has 100% description coverage, so there is no parameter burden. The baseline for no-parameter tools is 4, and the description correctly references the current session as the implicit context.

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?

"Get detailed information about the current Ableton session" clearly identifies a retrieval action with a specific resource. It does not explicitly distinguish itself from sibling info getters like get_track_info or get_arrangement_info, and "detailed information" is somewhat broad.

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?

Provides no guidance on when to use this tool versus sibling getters such as get_track_info, get_arrangement_info, or get_scenes. There is no mention of alternatives, exclusions, or typical use cases.

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