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

With no annotations, the description carries the full behavioral burden. Calling it an "export" implies a non-mutating read, and the enumerated contents tell the agent what is inside the payload, but it is silent on whether binary/media assets are excluded, on size or rate limits, and on any permission requirements.

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?

A single front-loaded sentence with no filler; the parenthetical inventory is long but each item adds real scope information. It stays readable and wastes nothing.

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 one-parameter, read-style tool with no annotations and no output schema, the description supplies the essential shape of the result (portable JSON) and its intended consumer (project.import). Missing are the exclusion rules for media assets and any note on payload scale, which matter for a full-structure dump.

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% and the sole parameter projectId has no description in the schema. The description does not name or explain it either, though "a project's full structure" makes the intent inferable; with only one required parameter the residual ambiguity is small.

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 ("Export a project's full structure") and enumerates exactly what is captured: settings, tracks, scenes, timeline, placeholders, transitions, current prompts. It also distinguishes itself from data-access siblings like project.get_state/get_summary by framing the output as a portable JSON document.

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 phrase "suitable for project.import" implies the round-trip use case and names the counterpart tool, which is useful routing. However, it never states when to choose export over project.get_state or project.get_summary, nor any precondition (ownership, project status) for calling it.

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