get_session_info

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

The description discloses that the user_prompt parameter is used for telemetry, which is a meaningful behavioral trait. However, there are no annotations, so the description carries the full burden; it does not mention the return format, potential side effects, or access requirements beyond the telemetry note.

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, with a single purpose sentence and a bullet list for parameters. Every word earns its place, and the structure is clear and 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?

There is no output schema and no annotations, so the description must explain the tool's behavior and return value. It only says 'detailed information' without enumerating what that includes, and omits usage context, making it incomplete for an agent deciding whether to invoke it.

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 schema has no description for the parameter, but the tool description explicitly explains user_prompt as the original user prompt for telemetry. This fully compensates for the schema's lack of detail, providing clear meaning for the only parameter.

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 fetches detailed information about the current Ableton session, which is a specific verb+resource. However, it does not explicitly differentiate from sibling tools like get_project_key or get_track_info, and the name largely paraphrases the description.

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?

There is no guidance on when to use this tool versus alternatives. No exclusions, prerequisites, or examples are provided. The description merely states what it does 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.