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

No annotations are provided, placing the full burden on the description. The description only states it lists videos, but fails to disclose behavioral traits such as output format, pagination, ordering, rate limits, or whether it returns all videos at once. This is insufficient for a 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?

The description is a single concise sentence with no unnecessary words. It is front-loaded with the key action and resource. However, it could include a brief note about what is returned without becoming wordy, so it is not maximally efficient.

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?

Given the tool has no parameters and no output schema, the description is minimally adequate for a simple list operation. However, it lacks any information about return format, whether the list is paginated, or what fields are included. An agent might need to infer or risk misinterpreting the output.

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?

The input schema has zero parameters with 100% documentation coverage. With no parameters, the baseline score is 4. The description does not need to add parameter semantics, and it correctly omits irrelevant details.

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', the resource 'videos', and the scope 'owned by the authenticated account'. This distinguishes it from sibling tools like viddler_videos_get (which likely retrieves a single video) and viddler_videos_create_upload (which creates). The purpose is specific and unambiguous.

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 that the tool is used to list all videos for the authenticated user, but it does not explicitly state when to use it versus alternatives like viddler_videos_get for specific video retrieval. No when-not or alternative guidance is provided, relying on implied context from sibling names.

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