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

Annotations already declare idempotentHint=true, destructiveHint=false, readOnlyHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the stateful side effect ('the editing tools then act on it') and visible UI behavior ('an open Vidova app shows it on screen'), but it omits what happens on an invalid id or whether it replaces the currently active project.

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 with the purpose front-loaded, followed by dependency and observable side effect. No filler, though the phrasing 'An open Vidova app shows it on screen' is slightly awkward and could be tightened.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. The description covers purpose, dependency on list_projects, and the observable effect; only error handling and interaction with an already-open project are unstated, which is a minor 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 description coverage is 0%, so the description carries the burden for the single projectId parameter. It usefully tells the agent where the id comes from ('from list_projects'), but says nothing about the expected format (UUID, slug, numeric) or failure behavior for an unknown id, leaving part of the gap unfilled.

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 ('Open a project by its id'), which cleanly separates it from create_project, list_projects and delete_project. It does not, however, distinguish itself from get_active_project or explain how 'open' differs from merely reading a project, so it stops short of full sibling differentiation.

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?

'The editing tools then act on it' implies the usage context: open this before performing edits. There is no explicit when-not guidance and no mention of the sibling get_active_project as an alternative for inspecting the current project, so the routing is only implied.

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