set_session_automation_record

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

The description adds context about the tool's purpose (toggle recording) and its relation to captured knob rides, but does not disclose additional behavioral traits beyond the annotations. With destructiveHint=false already indicating it's not destructive, the description adds moderate value.

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 wasted words. It efficiently conveys purpose and differentiation.

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 tool has low complexity (one boolean parameter) and an output schema exists. The description provides sufficient context for basic understanding, though it omits return value details. Given the output schema, this is acceptable.

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 compensate but only implies that 'enabled' controls the toggle. The boolean parameter is inherently simple, but more detail (e.g., what happens when enabled) would be helpful.

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 action ('Toggle recording of parameter changes') and the resource ('Session clip envelopes'). It also distinguishes itself from the sibling tool 'write_automation' by mentioning it's an alternative for 'captured knob rides'.

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 explicitly labels the tool as an alternative to write_automation for a specific use case ('captured knob rides'), providing clear context for when to use it. However, it does not explicitly state when not to use it or mention other alternatives.

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