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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description still adds real behavior beyond that: 'Only done means Premiere reported verified readback' and the caveat that cancelled requests may still finish — both are non-obvious polling semantics.

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?

Three short sentences, front-loaded with the outcome-read purpose followed by the state semantics and then the prerequisite. The prerequisite sentence slightly duplicates the deviceId schema description, a minor redundancy.

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 exists, so the description carries the burden of explaining return values — it clarifies only the 'done' state and says nothing about other terminal or in-progress states an agent must handle. For a polling-status tool this leaves a meaningful 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?

Schema coverage is 50%: deviceId is documented in the schema and the description reinforces its source, but requestId has no schema description and the description never says where it comes from (presumably premiere_request_edit). With half the parameters opaque, the description does not compensate.

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 and resource ('Read an edit outcome'), making the read-vs-request split inferable against premiere_request_edit. It never names a sibling explicitly, so the differentiation from aftereffects_edit_status-style tools is left to the name prefix.

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?

Provides a concrete prerequisite ('First call premiere_list_connections to get the deviceId'), which is genuinely actionable. However, it never states when to poll this versus premiere_cancel_edit or how often to call it, leaving the core polling workflow implied.

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