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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real value beyond that: "as last saved" discloses that the data is a snapshot rather than live, and "full=true also lists caption clips" discloses a behavior toggle.

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?

Very short and front-loaded, but the opening is a verbless fragment ("Tracks (top to bottom) and every clip..."), which reads awkwardly and slightly obscures the action. No wasted words, but structure is telegraphic rather than clean.

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 carries the return-value burden and does list the salient fields (id, kind, start, duration). For a 2-parameter read tool this is largely complete, though it says nothing about ordering guarantees, pagination, or error behavior.

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%: the 'project' param is documented in-schema, but 'full' is bare. The description compensates by explaining exactly what full=true does (includes caption clips), which is more than the schema provides. Could be a notch higher if it clarified default behavior when full is omitted.

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 title plus description make clear this reads a project's timeline: it returns tracks top-to-bottom and every clip with id, kind, start, and duration. The resource is distinct from siblings like edit_project or create_project, though the description never explicitly names those alternatives.

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?

"Use before editing" provides one concrete when-to-use hook, which is genuinely helpful for sequencing. However, there is no when-not guidance and no named alternative for read paths (e.g. view_media, list_edit_ops), so 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.