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

The description labels the tool '[read]', but the annotations declare readOnlyHint=false and destructiveHint=true. An agent reading the description would assume a harmless fetch, which directly conflicts with the declared safety profile; no other behavioral context is offered.

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?

A single short sentence with no filler, front-loaded with the tool's intent. The bracketed tag and the 'data = {...}' fragment are terse but readable; nothing is padded.

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 supply the return structure, which is the main thing an agent needs. But there is no usage context relative to sibling promo-video tools and the misleading '[read]' framing leaves the safety picture incomplete at best.

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 tool takes zero parameters, so the schema baseline is 4. The description adds the return shape (briefs, actions), which is useful but concerns output rather than inputs.

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 a concrete resource (suggested briefs and scene movements/actions from the promotion video form) and sketches the return shape (data = {briefs, actions}). However, it does not differentiate from the closely related siblings promo_video_concepts and promo_video_scenes, so an agent cannot tell which suggestion-style tool to pick.

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?

There is no statement of when to call this versus promo_video_concepts, promo_video_scenes, or create_promo_video. The '[read]' tag hints at retrieval, but no preconditions, ordering, or alternatives are given.

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