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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds real context beyond that: maxTokens truncates guidance content, and scaffold and component ignore maxTokens because they always return whole files. It does not mention auth, rate limits, or formatting of the guidance output, but for a read-only guide this is solid.

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 core purpose is front-loaded in the first clause, followed by the mode semantics and a short provenance note. Three dense sentences with little waste, though the trailing registry sentence is the least load-bearing.

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 does the job of explaining what each invocation shape returns and how truncation works. What is missing is workflow positioning relative to the video siblings, which matters given how many guide/plan/render tools exist, but everything needed to call this tool correctly is present.

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 100%, so the per-parameter docs already carry the load and the baseline is 3. The description earns the extra point by explaining mode interactions the schema does not: no arguments lists components, scaffold:true yields a whole project, component yields one component's source plus install command.

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 and resource: it returns best-practices guidance, brand/motion tokens, format profiles, and video components for building Remotion product demos in code. That is clearly distinguishable from most siblings, though it never names the adjacent video siblings (plan-video, render-video-frames) that an agent might also consider.

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?

'Start here when building a video' gives a genuine entry-point cue, and the mode sentences hint at when to use scaffold vs component vs no-argument listing. However, it offers no explicit routing against the other video tools in the sibling set (plan-video, render-video-frames), so the agent must infer the boundary itself.

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