list_stream_videos

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

With no annotations provided, the description carries the full burden of disclosing behavior. It states the basic list operation but gives no details about return structure, pagination, ordering, or account-scoping behavior. It is not misleading, but it is too thin to fully inform an agent.

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 a single, direct sentence with no wasted words. It is appropriately front-loaded, though it is concise partly because it omits potentially useful operational details.

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 list operation with one required parameter, the description is minimally adequate. However, with no output schema or annotations, it does not mention expected return format, pagination, or any account-level context beyond the parameter name, leaving minor but relevant gaps.

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 100%, and the single account_id parameter is already described as 'The account ID.' The tool description adds no additional meaning to the parameter, so the schema carries the semantic weight; the baseline of 3 is appropriate.

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 the verb ('List') and resource ('videos in Cloudflare Stream'), making the core purpose understandable. It does not explicitly differentiate from the sibling get_stream_video, but the contrast between listing and getting a specific video is reasonably inferable from the names.

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 guidance on when to use this tool versus alternatives such as get_stream_video, nor any mention of pagination, filtering, or other conditions. The agent must infer usage solely from the tool name and minimal description.

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