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

Annotations already mark this as read-only and non-destructive. The description adds useful behavioral context beyond annotations: the operation is free, returns videos newest-first, enforces a limit of 1..100, and includes specific fields like status and file_url.

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 description is extremely concise, with no filler. It front-loads the most valuable distinguishing detail ('Free') and packs ordering, range, and result fields into one efficient sentence.

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?

For a simple single-parameter list tool, the description is complete. Output schema covers the return shape, annotations cover safety, and the description explains the ordering, limit range, and included fields. No critical calling information is missing.

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 must compensate for the lone `limit` parameter. It does so by clarifying the valid range (1..100), which is absent from the schema, and by implying that limit controls how many videos are returned.

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 action and resource: listing the user's most recent videos. It adds specifics—newest first, limit range, and returned fields—that distinguish it from singular status-checking tools like tegas_video_status.

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 description implies when to use the tool: when you need a user's recent videos and their metadata. However, it does not explicitly mention alternatives or state when not to use it, such as checking a single video's status with tegas_video_status.

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