Screen recording status

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

Explicitly states 'Read-only', which is a key behavioral trait, and specifies the two outputs (activity status and file measurement). While no annotations exist, the read-only declaration covers the main side-effect concern. It does not mention permissions or exact return format, but that is less critical for a read-only tool.

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?

A single, focused sentence that front-loads the purpose ('Report...') and appends the read-only note. No wasted words, highly efficient.

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?

The description is adequate for a simple status tool, but 'measure the current output file' is ambiguous—it does not clarify whether it returns file size, duration, or path. Without an output schema, this ambiguity is not resolved, leaving a minor gap.

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 tool has zero parameters, and schema coverage is 100%. The description adds no parameter-specific details, but none are needed; baseline of 4 applies for zero-parameter tools.

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 states a specific action ('Report whether gpu-screen-recorder is active') and a measurable ('measure the current output file'), clearly distinguishing it from sibling start/stop tools by emphasizing the status and read-only nature.

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 implies its use case as a status check but does not explicitly contrast with screenrecording_start or screenrecording_stop. No when-not-to-use guidance or alternatives are provided; usage is left to inference.

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