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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real context beyond them: the newest-first ordering, the exact facets returned (video availability, project kind, shorts progress, parent relationships), and the caveat that navigation-pointer data does not determine the target of later project-scoped requests.

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, front-loaded with the core action and ordering, then the returned facets and a single caveat. No filler. The second sentence leans on jargon ('navigation-pointer information') that an agent may need to map to returned fields, which is the only mild cost.

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?

With no output schema, the description must convey what comes back, and it does by enumerating the per-project facets. For a parameterless read-only listing tool, nothing essential to a correct call appears to be missing; only result volume or truncation behavior goes unstated.

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 tool takes zero parameters, so there is no schema semantics to compensate for; the baseline for a parameterless tool applies. The description correctly does not invent filtering or pagination inputs that the empty schema would reject.

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 states a specific verb and resource ('Lists the authenticated account's video projects') plus ordering ('newest first') and the fields returned. It is easily separable from siblings like create_project, open_project or project_state, though it never names an alternative explicitly.

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?

Usage is only implied: an agent can infer this is the discovery step before open_project or project_state. There is no explicit when-to-use/when-not statement and no guidance on how this differs from project_state or list_assets for an agent that already knows the project.

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