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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds value by noting the operation is 'Cheap' and enumerating the components returned, giving the agent a sense of the response scope without contradicting the annotations.

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?

The description is two sentences, front-loads the verb and resource, and delivers the usage guidance in a compact second sentence. There is no wasted wording, and it is easy to parse.

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 simple read-only tool with one parameter and annotations covering safety, the description covers the core behavior, usage trigger, and the components included. It doesn't describe the exact response format, but the absence of an output schema is mitigated by the listed components.

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 schema defines project_id only as an integer with no description, and the tool description does not mention the parameter at all. With schema coverage at 0%, the description fails to compensate by explaining what project_id refers to, leaving the agent to infer its meaning from context.

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 'Re-read' and a resource 'explicit project's state' with a list of contained elements (video, transcript, shots, current EDL, assets). This clearly distinguishes it from sibling get_* tools that retrieve specific components, so an agent can immediately understand its scope.

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 description explicitly advises 'call it whenever you are unsure what the edit currently looks like' and labels it 'Cheap', providing a clear usage condition. It doesn't mention when not to use it or name alternatives, but the guidance is sufficient for a general-purpose state read.

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