start_record

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

No annotations are provided, so the description carries full burden. It states 'Start recording' but does not disclose behavioral traits such as side effects (file creation), error conditions (already recording), state requirements, or permissions. This is minimal disclosure for a state-changing action.

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?

At one sentence, the description is front-loaded and concise, but it is too minimal to effectively convey the tool's purpose. While it saves words, it sacrifices crucial information, making it under-sized rather than appropriately concise.

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 one optional parameter and no output schema, the description omits critical context such as the dry_run parameter, error handling, state prerequisites, and expected behavior. For a simple tool, this level of completeness is inadequate.

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 input schema includes a dry_run boolean parameter with 0% description coverage. The description does not mention this parameter at all, so the agent is unaware that a simulation mode exists. With a single parameter and no schema descriptions, the description fails to add necessary meaning.

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 'Start recording' clearly indicates the verb (start) and resource (recording), and it distinguishes this tool from siblings like stop_record, pause_record, and record_status. However, it is essentially a tautology of the tool name, lacking specificity about the context or scope of 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 description provides no guidance on when to use this tool versus alternatives, nor does it specify prerequisites (e.g., a scene must be active, OBS must be running). Sibling tools like stop_record or record_status imply usage context, but the description itself offers no such information.

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