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

Annotations already declare a safe read operation (readOnlyHint=true, destructiveHint=false, openWorldHint=false), but the description adds meaningful context beyond them: BETA status with a date, account-tier export limits (3 badged 720p for free, 2 clean/day for trials, unlimited for subscribers), and an approximate output size of ~100k chars. It stops short of describing structure or pagination of the large default response.

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?

Dense but front-loaded: capability scope, parameter behavior, then tier/beta notes. Every sentence carries information, though the BETA/tier sentence is long and could be tightened. No filler or tautology.

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 and only two optional params, the description covers what an agent needs: what the guide contains, how to narrow it, and when to call it. The tier-limit detail makes it more complete than a bare guide stub, though the shape of the ~100k-char return is only implied.

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%, so the description carries the burden and does explain both parameters: section=<part> returns one part and tool=<video tool> narrows the schemas, with the default being the whole guide. It does not enumerate the section enum values in prose, but the schema supplies those.

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 names the specific subject (Video Director) and enumerates exactly what the guide covers: capabilities, creative catalog, producer workflow, and every engine command's input schema. This clearly separates it from siblings like video_producer, video_strategies, and account_management_guide.

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?

Explicitly states when to call it: 'Call video_guide first for the catalog, the exact input schema of each action and this account's tier notes.' This routes the agent before it invokes mutation tools such as video_render or video_edit_apply.

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