get_session_info

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

With no annotations, the description carries the full burden. It clearly states the data returned (tempo, time signature, track counts, master track details), indicating no side effects. It could mention prerequisites (e.g., session must be open) but is adequate for a simple read operation.

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?

Single sentence with no wasted words. The key information (action, resource, specific fields) is front-loaded.

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 succinctly covers what the tool returns, and since an output schema exists, return values are fully documented elsewhere. No gaps.

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?

There are zero parameters, achieving 100% schema coverage trivially. The description does not need to add parameter info, so baseline 4 applies.

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 verb 'Get' clearly indicates retrieval, and the resource is specified as 'current Ableton Live session info' with explicit fields (tempo, time signature, track counts, master track details). This distinguishes it from sibling getters like get_clip_info or get_track_info.

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 use for obtaining session-level data but provides no explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned, which is acceptable given the tool's distinct purpose.

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