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

With no annotations, the description carries the full burden. It usefully discloses that this is a single-call aggregate reader and that media prompts/status come resolved, and the schema's includeMediaVersions note hints at payload-compaction behavior. However it says nothing about read-only safety, permissions, or how large a 'complete state' response can get for a big 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?

Two tight sentences with zero waste. The scope and payload are front-loaded before the efficiency claim, so an agent can stop reading after the first sentence and still know what it gets back.

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 aggregate fetch with no output schema, the description adequately covers what is returned (settings, scenes, shots, resolved media prompts/status). It is nearly complete, missing only sibling differentiation and any caution about response size, which touches on usage rather than capability.

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 100%, so editId, workspaceId, and includeMediaVersions are already documented in the schema, including the 'set true only when all historical media versions are required' guidance. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 ('Get complete project state') and enumerates the returned parts: edit settings, all scenes, all shots with resolved media prompts/status. It is clear what the tool does, but it never distinguishes itself from siblings like get_edit, list_scenes, or list_shots, so an agent must infer that this is the aggregate version.

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 closing sentence ('most efficient way to understand the full edit') implies when to reach for it, but there are no explicit exclusions or named alternatives. An agent is left to guess when a narrower call such as get_edit or list_shots would be cheaper or sufficient.

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