Get a bin's videos

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

With readOnlyHint=true already covering the safety profile, the description still adds real behavioral context: a bin can hold the whole catalog, so results are truncated to 50 by default and paging via offset is required. It does not mention ordering or what happens with an invalid binId.

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, zero waste, with the scoping statement front-loaded and the pagination caveat immediately after. Every clause 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?

For a three-parameter read tool with no output schema, the description covers the key trap (silent truncation at 50) and names the totalCount field the agent must inspect. It could be slightly more complete by noting there is no filtering here versus search_videos.

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%, so binId, limit and offset are already documented; the description mostly restates the default-50 and paging behavior. It adds the rationale (bins can be catalog-sized) and points at totalCount, which is mildly useful but not new parameter semantics.

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?

States a specific verb and resource ("List the videos collected in one bin"), which cleanly separates it from get_video (single video), list_bins, and search_videos. An agent can tell what this returns without opening the schema.

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 explains pagination mechanics (default 50, check totalCount, page with offset) but gives no explicit when-to-use versus alternatives such as search_videos or list_videos_needing_indexing. Usage is implied by the bin-scoped framing rather than stated.

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