List videos

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

The description adds ordering and pagination details beyond the readOnlyHint annotation. It does not cover potential errors or rate limits, but for a read operation this is sufficient.

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?

Two sentences with no wasted words. The purpose is front-loaded, and the pagination instruction is directly useful. Every sentence earns its place.

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?

The description covers core behavior and pagination but does not describe the output format or fields. However, for a simple list tool with no output schema, this is reasonably complete.

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?

With 100% schema coverage, the description adds value by clarifying offset usage ('pass the returned nextOffset') and limit default (20). This provides practical meaning beyond the schema alone.

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 states 'List videos in the Synthesia account' with a specific verb and resource. It distinguishes from sibling tools like list_avatars, list_templates, etc., by focusing on videos and mentioning ordering by newest context.

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 explains when to use the tool (to list videos) and provides pagination guidance, but does not explicitly mention when not to use it or compare to alternatives like search or filter. However, the context is clear for a basic list operation.

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