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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine value beyond that: it clarifies that nothing is written and that temporary files are removed, telling the agent exactly what the destructive action affects.

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?

Two tight sentences with the action front-loaded and the side effect following. Every clause carries information; nothing is wasted or buried.

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?

For a modest three-parameter mutation tool with no output schema, the description covers purpose and behavioral consequence well. Its one gap is not indicating the source of the required jobId, a minor omission against an otherwise complete definition.

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 67% (deviceId and workSessionId are documented inline, but the required jobId has no schema description). The description only implies jobId refers to a video job; it does not explain where to obtain it or its format, so it neither fully compensates for nor extends the schema. Baseline 3 is appropriate.

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?

States a specific verb ('Stop') and resource (a running video_edit or video_transcribe job), and explicitly names the two sibling tools whose jobs it targets. An agent can clearly differentiate this from cancel_workflow or stop_process without opening any schema.

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 scopes usage precisely to running video_edit/video_transcribe jobs, giving clear context for when to invoke it. It does not, however, name explicit alternatives (e.g. cancel_workflow) or state when-not-to-use, so it falls short of full routing guidance.

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