set_session_automation_record

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

With no annotations provided, the description carries the full burden. It transparently discloses that enabling records parameter changes during playback, which is the core behavior. No hidden side effects are hinted, and the simple boolean nature is clearly conveyed.

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 compact and front-loaded, with the main action in the first line, followed by a brief elaboration and a parameter explanation. Every sentence earns its place; no redundancy.

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's simplicity (one boolean parameter) and the presence of an output schema, the description is adequately complete. It specifies the action, the meaning of the parameter, and the behavioral consequence. It does not need to document return values due to the output schema, and no prerequisites or further context are obviously missing.

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 description adds meaning to the 'enabled' parameter beyond the schema's bare title. It explains 'True to enable, False to disable' and connects it to the real effect ('parameter changes during playback are recorded as automation'), which is helpful for the agent.

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 'Enable or disable session automation recording', identifying the specific verb and resource. It distinguishes from siblings like 'set_session_record' (session recording) and 'get_session_automation_record' (querying state), making the tool's purpose unambiguous.

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 explains the effect of enabling (parameter changes during playback are recorded) but does not explicitly state when to use this tool versus alternatives or mention that 'get_session_automation_record' exists for querying state. Usage context is implied but not explicit.

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