record

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states start/stop but fails to describe critical behaviors: what happens if recording is already in progress, whether the recording is saved automatically, or how to specify output path. The many parameters suggest complex setup but no hints are given.

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 6 words, the description is too brief and lacks structure. It does not front-load essential information such as required parameters or typical usage patterns, making it under-specified rather than 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's complexity (22 parameters, no output schema), the description is completely inadequate. It does not explain return values, side effects, error conditions, or dependencies like device selection or session management. The agent cannot reliably use this tool based on the description alone.

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 coverage is 77%, meaning 17 of 22 parameters have descriptions. The description adds no value beyond the schema, failing to explain key parameters like 'path', 'fps', 'quality', and 'hideTouches', which require additional context for correct usage.

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 the tool's purpose: 'Start or stop screen recording.' It identifies the verb (start/stop) and resource (screen recording), which is clear and direct. However, it does not differentiate from sibling tools like 'screenshot' or 'replay', which could lead to confusion in certain contexts.

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 is provided on when to use this tool versus alternatives such as 'screenshot' for capturing static images or 'replay' for recording interactions. The description lacks context about prerequisites (e.g., device booted) or when to use start vs stop.

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