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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful semantics about how section markers own content, what the protected video-playback token does, and when footage plays at section end. However, it omits any statement about permissions, size limits, or behavior when a project is missing or has no script.

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 purpose is front-loaded in the first sentence, which is good. But several sentences are dense and of unclear value to tool selection, notably 'The section and slide registries do not define playback adjacency' and the closing 'The Tutorial AI backend does not call another AI model,' which reads as an internal note rather than selection-relevant guidance.

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?

An output schema exists, so the extensive return-shape narration is largely redundant, but it does establish important conventions (authored document order, section ownership, playback fallback). Combined with readOnly annotations, an agent has enough to call it correctly; the only material gap is the undocumented projectUid.

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?

There is one required parameter, projectUid, and schema description coverage is 0%, so the description carries the full burden of explaining it. The description never mentions projectUid or what kind of identifier it expects (project UID vs. slug, where to obtain it). The remaining text is entirely about return structure.

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 concrete verb and resource: 'Read the complete script for rewriting by the LLM in this MCP session.' This distinguishes it from the mutation sibling rewrite_script by making clear it only fetches context. It does not explicitly contrast with get_document or get_project, so the differentiation is implied rather than spelled out.

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 'for rewriting by the LLM' implies the tool is a prerequisite read before a rewrite, but no explicit when/when-not guidance or named alternative is given. An agent must infer that this should be called before rewrite_script rather than after or instead of it.

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