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

Annotations already handle safety (`readOnlyHint: true`). The description enhances this by detailing operational metadata (shorts count, slot usage), which informs the agent about the resource's current state and usage patterns, adding significant context beyond standard safety hints.

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 two sentences are highly efficient; the first defines the resource and output, and the second defines operational constraints, making it succinct and professional.

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?

Given the lack of an output schema, the description provides crucial structural details about the returned data (specifically that it includes shorts data and slot usage) which makes the tool more complete than a generic 'list videos' call.

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%, meaning the schema defines the limits and offsets. The description does not add semantic meaning to the parameters (limit, offset, search), adhering to the baseline score for highly covered schemas.

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 clearly identifies the resource ('user's imported long videos'), the specific data points returned (id, title, status, shorts count, slot usage), and the sorting order ('newest first').

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?

It provides explicit guidance on downstream use: 'Use a video id with list_moments or clip_video.' This prevents the agent from misapplying the tool's output.

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