toggle_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 behavioral disclosure. It only restates the tool's name (toggle_record) with the phrase 'on/off' without explaining the state-dependent behavior (e.g., if recording, it stops; if not, it starts). This minimal detail adds little beyond the name itself.

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, concise sentence that is front-loaded with the key action. Every word is necessary, and there is no redundancy or unnecessary information.

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 with no parameters and no output schema, so a short description is acceptable. However, the description lacks explicit detail about the conditional behavior of toggling (what happens if already recording) and does not reference related tools, making it minimally complete but not fully informative for an agent.

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 tool has zero parameters, so the description is not required to add parameter semantics. With an empty schema, the baseline of 4 applies, as there are no parameter details to clarify.

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 'Toggle recording on/off.' uses a specific verb ('toggle') and resource ('recording') to clearly state the tool's function. It distinguishes itself from sibling tools like start_record, stop_record, and toggle_record_pause by indicating it flips the recording state between on and off.

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 implies usage when a user wants to switch the recording state, but it does not explicitly state when to choose this over start_record or stop_record. No alternative tools are mentioned, leaving the decision to the agent's inference from the verb 'toggle'.

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