List videos in your Vimeo library, newest first by default

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds value beyond those annotations by disclosing the trimmed return shape (id, name, duration, privacy, play count, folder, status) and the default sort order, which is the key behavioral fact for a list tool with no output schema.

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?

Three short sentences, zero filler. The scope and ordering (the most important selection cue) are front-loaded, followed by return shape and the sibling pointer.

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 paginated list tool with no output schema, the description compensates by enumerating the returned fields and the default ordering, and the annotations fully cover the read-only safety profile. Nothing an agent needs to call it correctly 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 coverage is 100%: all five parameters, including the sort and direction enums and their defaults, are documented in the schema itself. The description's only added parameter meaning is 'newest first by default', which merely restates the sort=date/direction=desc defaults. Baseline 3 applies when the schema does the heavy lifting.

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 videos in your Vimeo library') plus the default ordering ('newest first by default'). It also names the sibling it is not (get_video) and what shape it returns, so an agent can distinguish it from search_videos or get_video without opening a 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?

Explicitly routes the agent: 'Use get_video for the full object on one video' defines when to pick a sibling instead of this tool. It does not mention search_videos, which is the closest alternative for filtered lookups, so the when-not coverage is incomplete but clear as far as it goes.

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