start_screen_recording

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

With no annotations provided, the description carries full burden but provides minimal behavioral information. It mentions a default duration and return format, but doesn't disclose important behaviors like: whether recording starts immediately, what format/quality is used, where recordings are saved, if it requires specific permissions, or what happens when the limit is reached. The description doesn't contradict annotations (none exist).

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 appropriately brief and front-loaded with the core purpose. The Args/Returns structure is clear, though the 'Returns' section could be more specific than just 'Success or error message'. Every sentence serves a purpose with minimal waste.

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 this is a potentially complex system operation with no annotations and an output schema (though not shown), the description provides basic but incomplete coverage. It covers the parameter meaning and return format, but misses critical context about the recording behavior, storage location, permissions, and interaction with the sibling 'stop_screen_recording' tool.

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?

With 0% schema description coverage and only 1 parameter, the description adds meaningful context by explaining that 'limit' represents 'Maximum recording duration in seconds' and providing the default value of 180. This compensates well for the lack of schema descriptions, though it doesn't mention constraints like minimum/maximum values.

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 verb 'Start' and resource 'screen recording', making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'stop_screen_recording' in the description text itself, though the naming makes the distinction obvious.

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. There's no mention of prerequisites (like needing screen recording permissions), what happens if recording is already in progress, or when to use this versus other media-related tools like 'play_music' or 'get_screenshot'.

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