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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only adds 'Free' (likely a cost note) but fails to disclose pagination behavior, ordering, read-only nature, or side effects. This is insufficient for a tool with no annotation safety hints.

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 exceptionally concise, with two short sentences front-loading the purpose. 'Free' is a minor addition but does not waste words. Every sentence earns its place in terms of brevity.

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 tool has no output schema and no annotations, leaving the description to provide context. It fails to explain what 'videos' includes (e.g., metadata, pagination, ordering) or how it differs from sibling list tools. The description is too minimal to fully contextualize the tool's behavior in isolation.

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?

Both parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description adds no additional parameter-specific meaning beyond the schema, not even mentioning account_id or limit explicitly. It neither enhances nor detracts from the schema's clarity.

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 tool's function with a specific verb ('List') and resource ('videos for a specific account'), which distinguishes it from broader tools like list_videos. However, it does not explicitly name or contrast sibling tools, so it falls short of a 5.

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 phrase 'for a specific account' implies this tool should be used when targeting one account's videos, but it provides no explicit guidance on when to use it over alternatives like list_videos or get_video. No exclusions or alternative tool mentions are present.

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