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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the description need not repeat safety. It adds useful context about returning full state and the workflow requirement, but doesn't disclose any side effects or special edge cases beyond that. With annotations covering the safety profile, this is adequate but not rich.

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: the first states purpose and return content, the second gives a clear workflow directive. No fluff, information is front-loaded and each sentence earns its place.

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 read-only open tool with no output schema, the description explains what it returns and how to use the result. It doesn't mention how to get the initial project_id (e.g., from list_projects), but that's a minor gap given the tool's simple scope. Annotations cover safety, so nothing critical is missing.

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 0% and the only parameter project_id is an integer. The description mentions 'this project_id' but doesn't explain how to obtain it, what valid values are, or any format constraints. Since schema coverage is low, the description should compensate, but it doesn't add meaningful parameter semantics.

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 the tool opens a project for navigation and enumerates the returned state (video, transcript, shots, EDL, available items). It differentiates itself from siblings like list_projects (which lists) and project_state (which may just query) by emphasizing the full-state return and the navigation context.

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 instructs to copy the project_id into every later project-scoped call and notes that no other tool guesses from an active pointer. This tells the agent exactly when to use it and why it's the entry point, distinguishing it from alternatives.

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