get_session_info

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

The verb 'Get' clearly indicates a read-only operation, which is appropriate for a getter with no annotations. However, the description does not elaborate on what 'detailed information' entails, potential performance implications, or any caveats. It is minimally transparent but not misleading.

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 a single, front-loaded sentence with no filler. It is concise and easy to parse. However, it could be slightly more informative without sacrificing brevity, hence a 4 rather than a 5.

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?

With no output schema, no annotations, and no parameter details, the description is entirely responsible for conveying what the tool returns. It only says 'detailed information' without listing any specifics, leaving the agent uncertain about whether this tool is the right choice for a given task. This is a significant gap for a simple info getter.

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 no parameters and the schema is empty, so there is no parameter information for the description to supplement. The baseline score of 4 applies, and the description correctly avoids mentioning any non-existent parameters.

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 says 'Get detailed information about the current Ableton session', which essentially restates the tool name 'get_session_info'. 'Detailed information' is vague and does not specify what session properties are included, nor does it distinguish this from sibling getters like get_session_path or get_master_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?

No guidance is provided on when to use this tool versus other session-related getters. It does not mention alternatives or exclusions, leaving the agent without context for selection.

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