set_session_record

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'Arm/disarm session record mode' without explaining what that entails (e.g., begins recording, changes state). It does not mention side effects, permissions needed, or how it interacts with other recording states.

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 concise at one sentence, but it sacrifices important details. It is not front-loaded with key information; the purpose is clear but incomplete. While brevity is positive, the description could be longer to improve clarity without being verbose.

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 the tool has two parameters and no output schema or annotations, the description is insufficient. It does not explain the concept of 'session record mode', how the tool fits into the broader recording workflow, or what the expected outcome is. The description is minimally viable but leaves significant 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?

With 0% schema description coverage, the description should add meaning to the parameters. It does not explain the 'enabled' boolean parameter (e.g., true arms, false disarms). The 'ctx' parameter is also not described in the tool description, though its schema provides some context. The description adds minimal value beyond the schema.

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 'arm/disarm' and identifies the resource 'session record mode'. It is clear what the tool does and distinguishes it from sibling tools like get_session_record_status and other set_* tools. However, it is brief and lacks additional context about what 'session record mode' entails.

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 alternatives. The description does not explain the effect of the boolean parameter (true = arm, false = disarm) or indicate any prerequisites (e.g., track arming, playback state). This leaves the agent without clear usage direction.

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