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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond annotations: it returns sequence metadata including names, timing, and a revision, exposes readAt for freshness checking, and explicitly returns no footage bytes.

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 core purpose and followed by freshness guidance and the prerequisite. Every sentence carries useful information with no waste.

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 single-parameter read-only tool without an output schema, the description covers purpose, return content, freshness inspection, non-media behavior, and the prerequisite. Only minor gaps remain, such as whether there are pagination or error-handling concerns.

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 description coverage is 100% and the single deviceId parameter is fully documented in the schema. The description reinforces that it must come from premiere_list_connections but adds little parameter meaning beyond the schema itself.

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: reading the sequence shared by the user's Premiere panel, including names, timing, and revision. The scope is clear, but it does not explicitly distinguish itself from adjacent siblings such as premiere_frame or read_editor_timeline.

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 tells the agent to call premiere_list_connections first to obtain the required deviceId, which is a clear prerequisite. However, it does not state when to use this tool versus alternatives like premiere_frame or read_editor_timeline.

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