start_recording_gif

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the state-changing nature is known. The description adds nothing beyond that: it doesn't say whether an in-progress recording is interrupted, where the GIF is written, whether there is a duration/size cap, or how the capture is terminated — all material for a long-running capture operation.

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 front-loaded sentence with no filler or repetition. It is not padded, though the brevity reflects missing content rather than efficient packaging of complete content.

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?

No output schema, no parameters, and annotations cover only the safety profile, so the description carries the burden of explaining the lifecycle. It omits where the file lands, how to stop, and what happens if a recording is already running — the agent cannot complete the operation correctly without consulting siblings by guesswork.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The phrase "the screen" is the only scoping information, and it correctly signals full-screen capture with no monitor/region selection.

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?

Specific verb+resource+output format ("Start recording the screen as a GIF file"), which implicitly separates it from the sibling start_recording (presumably video). However it never names start_recording or explains the format difference explicitly, so the differentiation is inferred rather than stated.

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 choose GIF capture over start_recording, no prerequisites, and no mention that stop_recording must be called to finalize the file. The agent is left to infer the entire workflow from sibling names.

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