start_recording

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

Annotations are absent, so the description must carry the full burden. It only states the action without disclosing behavioral traits such as side effects (e.g., file creation, resource usage), required permissions, or whether it can be invoked multiple times. The single sentence is insufficient for an action that likely has significant state changes.

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 sentence, which is concise but at the expense of clarity. It could be expanded to include key information without becoming verbose. As it stands, it does not fully earn its place due to missing critical details.

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 that the tool has one optional parameter and an output schema (not shown), the description is incomplete. It fails to mention the return value, side effects, or how the parameter affects behavior. The description should provide enough context for the agent to use the tool correctly.

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 has 0% description coverage for its single parameter 'path'. The description does not explain the parameter's purpose, format, or effect. Without any elaboration, the agent cannot understand how to use the optional parameter or its default value.

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 video recording' clearly indicates the tool's action (start) and resource (video recording). It is distinct from sibling tools like stop_recording and recording_show_actions. However, it could be more specific about the scope (e.g., which tab or page).

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?

No guidance on when to use this tool vs alternatives like stop_recording or recording_show_actions. No prerequisites or context are provided. The agent receives no direction on appropriate use cases.

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