Quit Premiere (graceful)

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

Describes the graceful close mechanism (sending close signal, Premiere shows its own save prompt). Warns about data loss with force:true. Adds context beyond the destructiveHint annotation.

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 sentences conveying purpose, behavior, and usage. No wasted words. Front-loaded with core action.

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 no output schema and only two parameters, description fully covers what the tool does, its safety profile, and parameter requirements.

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?

Adds meaning to parameters beyond the schema: confirm must be true, force causes data loss. Schema already has 100% coverage, but description reinforces usage.

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?

Title and description clearly state the tool quits Premiere gracefully, distinguishing it from force quitting. The verb 'close' and resource 'Premiere' are specific.

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?

Explicitly states when to use confirm:true and when to use force:true, including warnings about data loss. Differentiates from sibling tools like premiere_restart.

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