as_screenrecord

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

The description implies a write operation ('record' and 'pull'), but annotations set readOnlyHint=true, creating a contradiction. No mention of permissions or side effects beyond the contradiction.

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?

Description is short, front-loaded, and includes an Args and Returns section. However, the Args section is redundant as the schema defines parameters. Still, no wasted sentences.

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 contradiction and lack of usage guidance, the description is incomplete. It does not explain why readOnlyHint is set when recording is not read-only, nor addresses potential side effects or required device state.

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 description coverage is 0% according to context. The description lists parameter names (out_path, seconds, serial) but adds no semantic detail beyond what the schema provides (e.g., that seconds is recording length). Does not compensate for missing schema descriptions.

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 it records the device screen to an .mp4 and pulls it to this PC. This distinguishes it from siblings like as_adb_screenshot (still image) and as_adb_logcat (logs).

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 versus alternatives (e.g., as_adb_screenshot for images) or any prerequisites or limitations (e.g., only works on devices with recording support).

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