verify_premiere_connection

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

The description explicitly states 'read-only' and 'without changing the project', clearly disclosing the non-destructive nature. It also mentions the report contents, providing transparency about the tool's behavior.

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?

The description is extremely concise—two short sentences—and contains no unnecessary detail. It is well-structured and directly to the point.

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 simple readiness check, the description covers all necessary aspects: what it does, when to use it, and what it reports. No additional information is required, and it is complete within its scope.

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 input schema has no parameters, so the baseline of 3 applies. The description does not need to add parameter details, and the tool's simplicity is well conveyed.

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 is a read-only readiness check for the CEP bridge and Premiere Pro host, and it distinguishes itself from sibling tools like 'ping' by covering the bridge and host state in detail (version, project, active sequence).

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?

It explicitly instructs to run before an editing workflow to confirm the bridge, giving clear usage context. However, it does not explicitly mention alternatives or when a lighter check like 'ping' might suffice, so it could be slightly more prescriptive.

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