set_recording

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

Annotations are absent, so the description carries the full burden. It only discloses the basic state change (enable/disable) but does not mention side effects, whether the operation is reversible, prerequisites like camera availability, the effect of using 'all', or return/error behavior. For a mutation tool this is a notable gap.

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?

One sentence with zero wasted words, front-loaded with the action and resource. The parenthetical scope is efficient and reinforces the optional 'all' behavior without 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?

The tool is simple and the input schema is rich, but there is no output schema or annotations, and the description says nothing about return values, error handling, or asynchronous behavior. It is minimally adequate for a toggle operation but leaves some operational context unstated.

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?

Schema description coverage is 100%, with both 'enabled' and 'printer' already fully described. The description's mention of '(or all printers)' merely restates what the schema's printer parameter already documents, adding no new semantic meaning beyond the structured input definitions.

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 a specific action ('Enable or disable'), a specific resource ('camera recording'), and a scope ('on a printer (or all printers)'). It distinguishes itself from camera-related siblings like set_camera_access (permissions) and set_timelapse (a different recording mode) by explicitly focusing on recording.

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 intended use is implied: use this when you want to toggle camera recording. However, there is no explicit guidance on when to use this tool versus alternative camera tools in the sibling list, such as set_camera_access or set_timelapse, and no mention of when not to use it.

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