toggle_session_record

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It merely states 'Toggle session record mode' without explaining what toggling does (e.g., starts/stops recording, affects session view), side effects, or state changes. This adds minimal value beyond the tool name.

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?

While the description is a single short sentence, it is under-specified rather than concise. It essentially restates the tool name without adding meaningful detail, so the sentence does not fully 'earn its place' as a valuable explanation.

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?

For a simple toggle operation with no parameters or annotations, the description is still incomplete. It does not explain the effect of toggling session record mode, how it relates to recording workflows, or what the user should expect. Given the lack of contextual signals, a more informative description is needed.

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 input schema has zero parameters, so the baseline is 4. The description does not need to explain parameters, and it does not introduce any ambiguity about the lack of inputs.

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 uses a specific verb 'toggle' and identifies the resource 'session record mode', which differentiates it from the sibling tool 'toggle_arrangement_record'. However, it does not explain what 'session record mode' entails, making the purpose clear but slightly incomplete.

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 provides no guidance on when to use this tool versus alternatives like 'toggle_arrangement_record', 'start_recording', or 'stop_recording'. There is no mention of context, prerequisites, or exclusions.

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